Skip to main content
Glama

byte-protocol

by io.github.0rkz

byte_list_feeds

Read-onlyIdempotent

List all active data feeds in the PayPerByte catalog with topics, price-per-call, and frequency (pricePerKB is a deprecated alias).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedsNoCatalog of active feeds

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedOutput schema / properties / feeds / items / properties / pricePerCall
      Added value: +{
+  "description": "Price of one call, atomic µUSDC (6 decimals), decimal string.",
+  "type": "string"
+}
    • changedOutput schema / properties / feeds / items / properties / pricePerKB / description
      Previous value: -"Price per KB in USDC (decimal string)"New value: +"DEPRECATED (misnamed): for gateway-fronted feeds this is the per-call price in µUSDC, identical to pricePerCall. Use pricePerCall. Removed next release."
  2. Changed5 schema fields changed
    • changedOutput schema / properties / feeds / items / properties / pricePerKB / description
      Previous value: -"Price per KB in USDC"New value: +"Price per KB in USDC (decimal string)"
    • changedOutput schema / properties / feeds / items / properties / pricePerKB / type
      Previous value: -"number"New value: +"string"
    • addedOutput schema / properties / feeds / items / properties / publisher
      Added value: +{
+  "description": "Publisher address for the feed",
+  "type": "string"
+}
    • removedOutput schema / properties / feeds / items / properties / slug
      Removed value: -{
-  "description": "Feed slug used in x402 routes",
-  "type": "string"
-}
    • removedOutput schema / properties / feeds / items / properties / status
      Removed value: -{
-  "description": "Feed status",
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "feeds": {
+      "description": "Catalog of active feeds",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "frequency": {
+            "description": "Expected publish cadence in seconds",
+            "type": "number"
+          },
+          "pricePerKB": {
+            "description": "Price per KB in USDC",
+            "type": "number"
+          },
+          "slug": {
+            "description": "Feed slug used in x402 routes",
+            "type": "string"
+          },
+          "status": {
+            "description": "Feed status",
+            "type": "string"
+          },
+          "topic": {
+            "description": "Topic identifier",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations: it filters to 'active' feeds and flags 'pricePerKB' as a deprecated alias, which helps agents interpret output correctly. No contradiction with annotations.

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?

A single, front-loaded sentence that communicates the action, scope, key output fields, and an important deprecation note. No filler or redundancy; every element earns its place.

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 parameterless read-only list operation with an output schema and comprehensive annotations, the description is complete. It clarifies the active-feed filter and deprecation detail, and nothing an agent needs to decide whether to call the tool is missing.

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

Parameters4/5

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

The tool has zero parameters, so the schema carries no burden; the baseline for 0 params is 4. The description does not need to explain parameters, though its mention of price-per-call and the deprecated alias adds useful output semantics rather than parameter semantics.

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?

Description uses a specific verb 'List' with a well-defined resource 'all active data feeds in the PayPerByte catalog' and names the included fields (topics, price-per-call, frequency). This clearly differentiates it from siblings like byte_list_my_subscriptions, which focus on user-specific subscriptions rather than the catalog.

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 phrase 'PayPerByte catalog' establishes this as the tool for browsing available feeds, contrasting implicitly with byte_list_my_subscriptions. However, it does not explicitly name alternatives or state when not to use the tool, so it falls short of a 5.

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

All byte-protocol toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct action or resource, and overlapping functions (buy_data vs subscribe, check_subscription vs list_my_subscriptions) are explicitly differentiated in descriptions. No two tools appear to do the same thing.

Naming Consistency4/5

Most tools follow the byte_verb_noun pattern (e.g., byte_buy_data, byte_get_publisher), but a few deviate: byte_subscription_health uses a noun phrase, and byte_unsubscribe lacks an explicit object. The consistent byte_ prefix keeps the set recognizable.

Tool Count5/5

15 tools is at the upper edge of the well-scoped range, and each tool serves a distinct purpose within the PayPerByte protocol—discovery, purchasing, publishing, verification, and account management. No redundant or filler tools.

Completeness4/5

Core lifecycle coverage is strong: list/search, subscribe/unsubscribe, buy, publish, register, verify, health, and network stats. Minor gaps exist, such as no explicit tool to fetch historical streamed messages or update a publisher schema, but these are workable.

Resources