Skip to main content
Glama

byte-protocol

by io.github.0rkz
OverviewDiscussionsAdmin

byte_publish_data

Destructive

Publish data to a subscriber via the PayPerByte DataStream contract. Hashes the payload, records size on-chain, and settles the fee in USDC. Requires PRIVATE_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesData payload to publish (will be hashed on-chain)
maxFeeYesMaximum fee in USDC willing to pay for this publish (e.g. 0.05)
subscriberYesSubscriber Ethereum address (0x...)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
txHashNoPublish transaction hash
successNoTrue if publish landed on-chain
payloadHashNokeccak256 of the payload as recorded on-chain
payloadSizeNoPayload size recorded on-chain (bytes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / error
      Removed value: -{
-  "description": "Error message if the operation failed",
-  "type": "string"
-}
    • removedOutput schema / properties / feePaid
      Removed value: -{
-  "description": "Actual USDC fee paid (atomic)",
-  "type": "string"
-}
    • addedOutput schema / properties / payloadSize
      Added value: +{
+  "description": "Payload size recorded on-chain (bytes)",
+  "type": "number"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "description": "Error message if the operation failed",
+      "type": "string"
+    },
+    "feePaid": {
+      "description": "Actual USDC fee paid (atomic)",
+      "type": "string"
+    },
+    "payloadHash": {
+      "description": "keccak256 of the payload as recorded on-chain",
+      "type": "string"
+    },
+    "success": {
+      "description": "True if publish landed on-chain",
+      "type": "boolean"
+    },
+    "txHash": {
+      "description": "Publish transaction hash",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations by explaining what the action entails: 'Hashes the payload, records size on-chain, and settles the fee in USDC.' This is consistent with the destructiveHint and readOnlyHint in the annotations, and it discloses the side effects clearly.

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 three sentences, front-loaded with the primary action, and every sentence adds value. It is concise without excessive detail, making it easy for an agent to quickly grasp the tool's purpose and key behavior.

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

Completeness4/5

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

Given the tool's complexity (a write operation with fee settlement), the description covers the essential behavioral aspects: hashing, on-chain recording, fee settlement, and the private key requirement. The presence of an output schema and full parameter descriptions fills the remaining gaps, making this reasonably complete.

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?

All three parameters are fully described in the input schema, so the description does not need to add parameter-level details. The description's mention of hashing and settling fees partially clarifies the purpose of 'data' and 'maxFee', but does not significantly exceed what the schema already provides. Thus, baseline of 3 is appropriate.

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 the action: 'Publish data to a subscriber via the PayPerByte DataStream contract.' This is a specific verb and resource that distinguishes it from sibling tools like 'subscribe' or 'buy_data'. The purpose is unambiguous.

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

Usage Guidelines3/5

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

The description implies that this tool is used to publish data to a subscriber, but it does not explicitly state when to use it versus alternatives. It does mention a prerequisite ('Requires PRIVATE_KEY'), which provides some usage context, but there is no explicit guidance on when to prefer this tool over other byte_* tools.

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

Resources