Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

Where does this number come from?

onchain_agent_explain_number
Read-onlyIdempotent

USE WHEN the question is where a published Sato Hub number comes from (ANSWERS ONE QUESTION) and you need its method, sample and reproduce call before quoting it. NOT FOR fresh measurements (use onchain_agent_get_agent_economy instead) or how old a data surface is (use onchain_agent_get_data_freshness).

RETURNS: for any https://satohub.ai/numbers/ page { slug, page, question, method, window, reproduce, mcp_server, rules } — how the number is measured and the exact call that reruns it. Otherwise it returns one finding from the State of Onchain Agents report by slug — the figure with its stage, method, sample, as-of date, the SQL query that reproduces it, and its citable page at https://satohub.ai/numbers/.

RULE ENFORCED: a number never travels without its stage, method, sample and date; it is never summed across venues, chains or stages. CITE THE URL in the payload, not this response. Returns an error while the report is unpublished.

RETURNS (json): { slug, title, number, unit, stage, method, sample, lines, query, as_of, url, cite, rules }. Read-only.

Example: { slug: "erc-8004-registered-agents" }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "onchain_agent_explain_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe finding's slug — the last path segment of a satohub.ai/numbers/<slug> URL.
response_formatNoText format; structuredContent is JSON either way.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / response_format / description
      Previous value: -"Output format: 'markdown' (default) or 'json'."New value: +"Text format; structuredContent is JSON either way."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the governing rule (a number never travels without stage, method, sample and date; never summed across venues/chains/stages), the citation requirement pointing at the URL rather than the response, and an error condition while the report is unpublished. That is behavioral context the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The USE WHEN / NOT FOR / RETURNS / RULE ENFORCED structure is front-loaded and scannable. However, returns are described twice (prose and a labeled "RETURNS (json)" block) with overlapping field lists, which is mild duplication rather than added value.

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 output schema, the description carries the full burden and does: it gives both possible return shapes, the key fields an agent needs to quote the number (stage, method, sample, as_of, query, cite), and the failure mode. Nothing needed to call or quote this tool is missing.

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 description coverage is 100%, so slug and response_format are already documented in the schema; baseline is 3. The description adds an example slug value and explains that slugs apply both to satohub.ai/numbers pages and to report findings, but it does not add format or constraint detail beyond the 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 names a specific verb and resource: it returns the method, sample, window and reproduce call behind a published Sato Hub number identified by slug. It also explicitly separates itself from onchain_agent_get_agent_economy (fresh measurements) and onchain_agent_get_data_freshness (surface age), so an agent can route correctly without opening a schema.

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?

It states the exact trigger ("USE WHEN the question is where a published Sato Hub number comes from") and the exact exclusions with named alternatives for each case. It even constrains the scope to answering one question, which prevents over-broad use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.