Skip to main content
Glama
0rkz

PayPerByte

by 0rkz
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

byte_query_fact

Submit a factual question to a live oracle publisher, pay per byte, and get a signed answer with citation URLs. Verify provenance from the on-chain receipt, then check the cited sources for accuracy.

Instructions

Query a PayPerByte fact-oracle publisher for a signed answer with citations. Posts the question to a registered fact-oracle publisher (topic='fact-oracle'), waits for the on-chain BroadcastStreamed response, and returns the answer plus structured citation URLs. The signed receipt proves which publisher produced the answer (provenance + tamper-evidence), NOT that the answer is correct — ground your output in the cited sources, not in a truth guarantee. Availability: this requires a registered fact-oracle publisher actively broadcasting; if none is live the call returns a timeout rather than an answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesThe factual question to ask (e.g. 'What was last night's Lakers vs Warriors score?'). Should be specific and verifiable.
topic_filterNoOptional topic filter (e.g. 'fact-oracle' default; future: 'sports', 'finance').
max_byte_costNoMax response payload bytes you're willing to pay for (defaults to 2000, ≈$1 at $0.0005/byte). Publisher refuses if can't fit answer.
min_publisher_pqsNoMinimum PQS to consider (BPS scale, 0-10000). 9000 = Elite-only, 7500 = Premium+.
subscriber_addressYesYour wallet address. You MUST be subscribed to the chosen publisher (with sufficient USDC escrow) or the publisher's on-chain broadcast will be skipped.
max_response_latency_msNoMax time to wait for the publisher's broadcast (default 30000 ms). Local-LLM publishers (Ollama + Searxng + 3-sample NLI gate) take ~30-60s; Anthropic + passthrough takes ~10-20s. Hard ceiling 180s.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if the query failed (no eligible publisher, broadcast timeout, etc.)
answerNoPublisher's grounded answer to the question
citationsNoURLs/sources cited by the publisher in support of the answer
confidenceNoPublisher-reported confidence (0-1)
elapsed_msNoEnd-to-end time to obtain the answer (ms)
request_idNoRequest id binding the query to this answer
payload_hashNokeccak256 of the response payload
publisher_pqsNoPublisher quality score (PQS) at fulfillment
publisher_addressNoPublisher address that fulfilled the query
response_size_bytesNoSize of the response payload (bytes)
publisher_tx_or_statusNoDelivery status or settlement reference

Schema Changelog

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

  1. Changed15 schema fields changedv0.10.7
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / citations / description
      Previous value: -"URLs cited by the publisher in support of the answer"New value: +"URLs/sources cited by the publisher in support of the answer"
    • removedOutput schema / properties / citations / items / type
      Removed value: -"string"
    • addedOutput schema / properties / confidence
      Added value: +{
+  "description": "Publisher-reported confidence (0-1)",
+  "type": "number"
+}
    • addedOutput schema / properties / elapsed_ms
      Added value: +{
+  "description": "End-to-end time to obtain the answer (ms)",
+  "type": "number"
+}
    • removedOutput schema / properties / feePaid
      Removed value: -{
-  "description": "USDC fee paid for the broadcast (atomic)",
-  "type": "string"
-}
    • removedOutput schema / properties / payloadHash
      Removed value: -{
-  "description": "keccak256 of the response payload",
-  "type": "string"
-}
    • addedOutput schema / properties / payload_hash
      Added value: +{
+  "description": "keccak256 of the response payload",
+  "type": "string"
+}
    • removedOutput schema / properties / publisher
      Removed value: -{
-  "description": "Publisher address that fulfilled the query",
-  "type": "string"
-}
    • addedOutput schema / properties / publisher_address
      Added value: +{
+  "description": "Publisher address that fulfilled the query",
+  "type": "string"
+}
    • addedOutput schema / properties / publisher_pqs
      Added value: +{
+  "description": "Publisher quality score (PQS) at fulfillment",
+  "type": "number"
+}
    • addedOutput schema / properties / publisher_tx_or_status
      Added value: +{
+  "description": "Delivery status or settlement reference",
+  "type": "string"
+}
    • addedOutput schema / properties / request_id
      Added value: +{
+  "description": "Request id binding the query to this answer",
+  "type": "string"
+}
    • addedOutput schema / properties / response_size_bytes
      Added value: +{
+  "description": "Size of the response payload (bytes)",
+  "type": "number"
+}
    • removedOutput schema / properties / txHash
      Removed value: -{
-  "description": "BroadcastStreamed transaction hash",
-  "type": "string"
-}
  2. Addedv0.10.5

TDQS

A5/5.0
Behavior5/5

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

The description discloses key behaviors: posts a question, waits for broadcast, returns answer + citations. Emphasizes that signed receipt proves provenance, not answer correctness. Also provides latency estimates. No contradiction with annotations (readOnlyHint=false, openWorldHint=true).

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?

Concise yet comprehensive: 5-6 sentences covering purpose, process, caveats, and parameter specifics. No wasted words; front-loaded with purpose.

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?

Given the tool's complexity (6 params, output schema exists), the description covers all essential aspects: what it does, how it works, caveats, parameter meanings, and publisher availability. Output schema presumably handles return values, so no gap.

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

Parameters5/5

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

Even with 100% schema coverage, the description adds meaningful context for all parameters: question (specific/verifiable), topic_filter (default), max_byte_cost (cost estimation), min_publisher_pqs (BPS scale), subscriber_address (subscription requirement), max_response_latency_ms (typical times). Goes beyond 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 clearly states the tool's purpose: query a fact-oracle publisher for a signed answer with citations. It distinguishes from sibling tools (e.g., searching publishers, subscribing) by focusing on the querying process.

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

Usage Guidelines5/5

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

Explicitly states when to use (need a signed answer with citations) and prerequisites (must be subscribed to a publisher). Also explains caveats like availability and timeout, and mentions the proof vs. correctness distinction.

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