Skip to main content
Glama

byte_register_publisher

Destructive

Become a data publisher on PayPerByte by registering your topic, payload specs, and price on-chain. Requires PRIVATE_KEY.

Instructions

Register as a data publisher on PayPerByte. Registers a schema and the publisher on-chain. Requires PRIVATE_KEY. PayPerByte v1 publishers are first-party and unstaked — leave stake at '0'; a non-zero USDC stake is approved to DataRegistry first if you choose to post one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stakeYesUSDC reputation stake to post, as a decimal string. Default '0' — PayPerByte v1 publishers are unstaked.
topicYesData feed topic (e.g. 'eth-price', 'weather-nyc', 'gas-tracker')
expectedSizeYesExpected payload size in bytes per message
maxSizeYesMaximum payload size in bytes per message
frequencyYesExpected publishing frequency in seconds
pricePerKBYesPrice per kilobyte in USDC (e.g. 0.003)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue if registration landed on-chain
txHashNoPublisher-registration transaction hash
schemaTxHashNoSchema-registration transaction hash
approveTxHashNoUSDC stake approval tx hash, if a non-zero stake was posted
publisherNoRegistered publisher address (the signer)
stakeUsdcNoUSDC stake posted (decimal string; '0' for v1 first-party)
topicNoRegistered feed topic
Behavior4/5

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

The description adds context beyond annotations by disclosing that registration is on-chain and requires a private key. Annotations indicate destructiveHint=true and readOnlyHint=false, which align with the description. No contradictions.

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 two sentences long, front-loads the purpose, and every sentence adds value. No wasted words.

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 that an output schema exists (indicated by context signals), the description does not need to explain return values. It covers the main purpose, prerequisites, and key behavioral nuance about stake. It is sufficiently complete for a registration tool.

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 coverage is 100%, so the schema already describes all parameters. The description adds meaningful extra detail for the stake parameter (default value and behavioral nuance) but does not add beyond the schema for other parameters. Baseline 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 'Register as a data publisher on PayPerByte' with a specific verb and resource. It distinguishes itself from siblings like byte_publish_data and byte_get_publisher by focusing on registration.

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 gives explicit guidance on stake usage ('leave stake at '0'') and notes that a non-zero stake requires prior approval. It also mentions the requirement for PRIVATE_KEY. However, it does not explicitly state when to use this tool versus alternatives.

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