byte-protocol

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

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`feeds`	No	Catalog of active feeds

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

changedOutput schema / properties / feeds / items / properties / pricePerCall / description

Previous value: -"Per-call price exactly as the gateway catalog reports it — a dollar-formatted string (examples: '$0.0050', '$0.100'); empty string if the catalog omits a price. This server does not normalize or convert it, so do not assume atomic units. The 402 challenge is the source of truth for what you will actually pay."New value: +"Per-call price exactly as the gateway catalog reports it — normally the catalog's `price`, a dollar-formatted string (examples: '$0.0050', '$0.100'); if the catalog supplies only `priceAtomic`, that atomic µUSDC value (e.g. '5000') passes through instead; empty string if it supplies neither. This server does not normalize or convert it, so do not assume either unit. The 402 challenge is the source of truth for what you will actually pay."

changedOutput schema / properties / feeds / items / properties / pricePerKB / description

Previous value: -"DEPRECATED (misnamed): identical to pricePerCall — the same gateway-reported per-call price, not a per-KB rate. Use pricePerCall. Removed next release."New value: +"DEPRECATED (misnamed): identical to pricePerCall — the same gateway-reported per-call price, not a per-KB rate. Use pricePerCall. Removal is scheduled for a future minor, not before 0.14."

Changed2 schema fields changedSep 13, 2026

changedOutput schema / properties / feeds / items / properties / pricePerCall / description

Previous value: -"Price of one call, atomic µUSDC (6 decimals), decimal string."New value: +"Per-call price exactly as the gateway catalog reports it — a dollar-formatted string (examples: '$0.0050', '$0.100'); empty string if the catalog omits a price. This server does not normalize or convert it, so do not assume atomic units. The 402 challenge is the source of truth for what you will actually pay."

changedOutput schema / properties / feeds / items / properties / pricePerKB / description

Previous value: -"DEPRECATED (misnamed): for gateway-fronted feeds this is the per-call price in µUSDC, identical to pricePerCall. Use pricePerCall. Removed next release."New value: +"DEPRECATED (misnamed): identical to pricePerCall — the same gateway-reported per-call price, not a per-KB rate. Use pricePerCall. Removed next release."

Changed2 schema fields changedSep 4, 2026

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."

Changed5 schema fields changedJun 11, 2026
- 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"
-}
```

Changed1 schema field changedMay 27, 2026

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"
+}

First observedMay 25, 2026

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, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context: only 'active' feeds are returned, and it discloses that pricePerKB is a deprecated alias, which prevents agents from misinterpreting that field.

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 entire description is one focused sentence with no filler. The core action and scope are front-loaded, and the deprecated-alias note is appended without bloating the text.

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?

With no parameters, an output schema present, and annotations covering safety, the description provides all necessary context: what is listed, the filtering ('active'), and what fields the agent should expect. Nothing essential 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?

There are zero parameters, so the baseline is 4 and there is nothing to explain. The description's mention of returned fields like topics and price-per-call is helpful even though it is technically 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?

The description clearly states a specific verb ('List'), a distinct resource ('all active data feeds in the PayPerByte catalog'), and summarizes the returned information. It distinguishes this from sibling tools like byte_list_my_subscriptions by emphasizing the catalog-wide scope.

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 'all active data feeds in the PayPerByte catalog' gives clear context for when to use this tool: when an agent needs a catalog-wide overview rather than user-specific subscriptions or publisher details. It does not explicitly name alternatives or state when not to use it, but the context is strong enough.

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

All byte-protocol tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

byte_list_feeds

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources