Skip to main content
Glama
0rkz

PayPerByte

by 0rkz
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

byte_list_my_subscriptions

Read-onlyIdempotent

List active subscriptions for a wallet to review publisher, topic, status, message counts, USDC spent, and last message time. See what you're paying for and decide whether to unsubscribe.

Instructions

List every active subscription for a given wallet address. Each entry has the publisher address, topic, status, when you subscribed, messages received in 7/30 days, USDC spent in 7/30 days, and the timestamp of the last message received. Use this to see what you're currently paying for and decide whether to unsubscribe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexerUrlNoOptional indexer URL override (default: INDEXER_URL/BYTE_INDEXER_URL env or https://feeds.payperbyte.io)
subscriberYesWallet address to list subscriptions for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionsNoActive subscriptions for the given wallet

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.11.13
    • removedOutput schema / properties / subscriptions / items / properties / lastMessageAt / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / subscriptions / items / properties / lastMessageAt / type
      Added value: +[
+  "number",
+  "string",
+  "null"
+]
    • removedOutput schema / properties / subscriptions / items / properties / status / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "number"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / subscriptions / items / properties / status / type
      Added value: +[
+  "string",
+  "number",
+  "null"
+]
    • removedOutput schema / properties / subscriptions / items / properties / subscribedAt / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / subscriptions / items / properties / subscribedAt / type
      Added value: +[
+  "number",
+  "string",
+  "null"
+]
  2. Changed12 schema fields changedv0.10.7
    • changedInput schema / properties / indexerUrl / description
      Previous value: -"Optional indexer URL override (default: BYTE_INDEXER_URL env or http://localhost:8080)"New value: +"Optional indexer URL override (default: INDEXER_URL/BYTE_INDEXER_URL env or https://feeds.payperbyte.io)"
    • addedOutput schema / properties / subscriptions / items / properties / lastMessageAt / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / subscriptions / items / properties / lastMessageAt / type
      Removed value: -"number"
    • addedOutput schema / properties / subscriptions / items / properties / spend30dUsdc
      Added value: +{
+  "description": "USDC spent in last 30 days (decimal string)",
+  "type": "string"
+}
    • addedOutput schema / properties / subscriptions / items / properties / spend7dUsdc
      Added value: +{
+  "description": "USDC spent in last 7 days (decimal string)",
+  "type": "string"
+}
    • removedOutput schema / properties / subscriptions / items / properties / spent30d
      Removed value: -{
-  "description": "USDC spent in last 30 days (atomic)",
-  "type": "string"
-}
    • removedOutput schema / properties / subscriptions / items / properties / spent7d
      Removed value: -{
-  "description": "USDC spent in last 7 days (atomic)",
-  "type": "string"
-}
    • addedOutput schema / properties / subscriptions / items / properties / status / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / subscriptions / items / properties / status / description
      Previous value: -"Subscription status"New value: +"Subscription status (string label or numeric code)"
    • removedOutput schema / properties / subscriptions / items / properties / status / type
      Removed value: -"string"
    • addedOutput schema / properties / subscriptions / items / properties / subscribedAt / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / subscriptions / items / properties / subscribedAt / type
      Removed value: -"number"
  3. Addedv0.10.5

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior. The description adds behavioral detail beyond annotations by explaining that it returns all active subscriptions with specific per-entry fields, and frames the operation as a read-only review activity. No contradictions found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: first the operation, then the exact output fields, then the intended use. Every sentence earns its place with no redundant phrasing or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list-type read-only tool with a rich output schema and complete annotations, this description is sufficient. It tells the agent what the tool returns, why it should be used, and provides enough context alongside the schema for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both `subscriber` and `indexerUrl` are already documented in the schema. The description only reiterates that the wallet address is used to list subscriptions, adding little semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation: 'List every active subscription for a given wallet address.' It precisely identifies the resource (subscriptions), the scope (active, per wallet), and even enumerates the returned fields. This clearly separates it from sibling tools like byte_check_subscription, which checks an individual subscription.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear when-to-use statement: 'Use this to see what you're currently paying for and decide whether to unsubscribe.' It does not explicitly mention alternative tools or exclusions, but the context is unambiguous for the primary use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0rkz/byte-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server