Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

by ai.satohub
OverviewDiscussionsAdmin

Is this going up or down?

onchain_agent_get_trend
Read-onlyIdempotent

USE WHEN the question is whether a measurement is going up or down (ANSWERS ONE QUESTION). Returns a bounded series (at most 30 points, default 8) for ONE venue, ONE chain and ONE stage from Sato Hub's own weekly (or daily) chain reads, each point with its date, value, sample_size and method. NOT FOR this week's numbers across venues (use onchain_agent_get_agent_economy instead) or one listing's score or check history (use onchain_agent_get_listing_history).

Pass stage (required). Venue is optional: name it to read exactly one series; omit it and a stage that only one venue reports is read from that venue, while a stage several venues report comes back as one SEPARATE series per venue. Stages by venue: erc8004 reports registered (weekly), registered_new_1d (daily), active_7d, mcp_endpoint_answers; olas reports registered and working; virtuals reports launched; virtuals_acp reports jobs_created; x402 reports settled_to_catalogued_seller, answers_402 (weekly) and facilitator_txs_1d_known (daily). A stage name alone is enough when one venue reports it; when several do (registered is reported by more than one venue) you get one separate series per venue.

RULE ENFORCED: points are never summed across venues, chains or stages — the tool refuses to blend chains and tells you which chains exist when you omit one, and several venues are never combined. A null point is UNKNOWN for that period, never zero. The weekly point is the citable one; daily points feed a trend and never a headline. Raw rows are not returned.

RETURNS (json): { venue, chain, stage, grain, unit, points: [{ date, value, sample_size, method, evidence_tier }], direction_first_to_last, known_points, rules, as_of, source } — or, when a stage several venues report is asked without a venue, { stage, grain, series: [that same object per venue], needs_chain?, no_reading?, rules }. Read-only.

Examples:

  • "are ERC-8004 registrations on Base growing" -> { venue: "erc8004", chain: "Base", stage: "registered" }

  • "how is registered trending on Base" (no venue) -> { stage: "registered", chain: "Base" }

  • "x402 sellers week over week" -> { venue: "x402", chain: "Base", stage: "settled_to_catalogued_seller", points: 12 }

  • "do registered endpoints answer, day by day" -> { venue: "erc8004", chain: "Base", stage: "mcp_endpoint_answers", grain: "daily", points: 30 }

Input Schema

NameRequiredDescriptionDefault
modeNo'stage' (default) is one venue/chain/stage series. 'movers' is the week's Sato Score movement across the directory — which listings rose, fell, crossed a tier, were scored for the first time, or answered our daily checks differently. In movers mode venue, chain and stage are ignored.stage
chainNoChain, e.g. Base, Ethereum, Gnosis. Required when a venue's stage is measured on more than one chain — series are never blended across chains. Omit for venue-level rows.
grainNo'weekly' (the citable series, default) or 'daily' (the trend grain; never a headline).weekly
stageNoLifecycle stage. When omitted, the default stage 'registered' is served (labelled defaulted), one series per venue and chain. By venue: erc8004 = registered, registered_new_1d (daily), active_7d, mcp_endpoint_answers; olas = registered, working; virtuals = launched; virtuals_acp = jobs_created; x402 = settled_to_catalogued_seller, answers_402, facilitator_txs_1d_known (daily).
venueNoVenue id: erc8004, olas, virtuals, virtuals_acp, x402, erc4337_accounts. Optional: when omitted, a stage that one venue reports is read from that venue, and a stage several venues report (registered) returns one separate series per venue. Pass it to read exactly one. See onchain_agent_get_agent_economy for the catalogue.
pointsNoHow many most-recent points (1-30, default 8).
response_formatNoText format; structuredContent is JSON either way.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / stage / description
      Previous value: -"Lifecycle stage. REQUIRED in 'stage' mode. By venue: erc8004 = registered, registered_new_1d (daily), active_7d, mcp_endpoint_answers; olas = registered, working; virtuals = launched; virtuals_acp = jobs_created; x402 = settled_to_catalogued_seller, answers_402, facilitator_txs_1d_known (daily)."New value: +"Lifecycle stage. When omitted, the default stage 'registered' is served (labelled defaulted), one series per venue and chain. By venue: erc8004 = registered, registered_new_1d (daily), active_7d, mcp_endpoint_answers; olas = registered, working; virtuals = launched; virtuals_acp = jobs_created; x402 = settled_to_catalogued_seller, answers_402, facilitator_txs_1d_known (daily)."
  2. 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"
  3. Changed3 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain, e.g. Base, Ethereum, Gnosis. Required when the stage is measured on more than one chain — series are never blended across chains. Omit for venue-level rows."New value: +"Chain, e.g. Base, Ethereum, Gnosis. Required when a venue's stage is measured on more than one chain — series are never blended across chains. Omit for venue-level rows."
    • changedInput schema / properties / stage / description
      Previous value: -"Lifecycle stage, e.g. registered, launched, settled_to_catalogued_seller, mcp_endpoint_answers. Required in 'stage' mode."New value: +"Lifecycle stage. REQUIRED in 'stage' mode. By venue: erc8004 = registered, registered_new_1d (daily), active_7d, mcp_endpoint_answers; olas = registered, working; virtuals = launched; virtuals_acp = jobs_created; x402 = settled_to_catalogued_seller, answers_402, facilitator_txs_1d_known (daily)."
    • changedInput schema / properties / venue / description
      Previous value: -"Venue id, e.g. erc8004, olas, virtuals, x402, erc4337_accounts. See onchain_agent_get_agent_economy for the catalogue."New value: +"Venue id: erc8004, olas, virtuals, virtuals_acp, x402, erc4337_accounts. Optional: when omitted, a stage that one venue reports is read from that venue, and a stage several venues report (registered) returns one separate series per venue. Pass it to read exactly one. See onchain_agent_get_agent_economy for the catalogue."
  4. 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."
  5. Changed5 schema fields changed
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "stage",
+  "description": "'stage' (default) is one venue/chain/stage series. 'movers' is the week's Sato Score movement across the directory — which listings rose, fell, crossed a tier, were scored for the first time, or answered our daily checks differently. In movers mode venue, chain and stage are ignored.",
+  "enum": [
+    "stage",
+    "movers"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / stage / description
      Previous value: -"Lifecycle stage, e.g. registered, launched, settled_to_catalogued_seller, mcp_endpoint_answers."New value: +"Lifecycle stage, e.g. registered, launched, settled_to_catalogued_seller, mcp_endpoint_answers. Required in 'stage' mode."
    • removedInput schema / properties / stage / minLength
      Removed value: -1
    • removedInput schema / properties / venue / minLength
      Removed value: -1
    • removedInput schema / required
      Removed value: -[
-  "venue",
-  "stage"
-]
  6. Added

TDQS

A4.7/5.0
Behavior5/5

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

The annotations only cover read-only/idempotent safety, but the description adds substantial behavior: points are never summed across venues/chains/stages, the tool refuses to blend chains and reports which chains exist, null means UNKNOWN not zero, weekly is the citable grain and daily is never a headline, and raw rows are withheld. That is rich disclosure well beyond what annotations provide.

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

Conciseness3/5

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

It is front-loaded and information-dense, but the multi-venue rule is stated twice ('A stage name alone is enough when one venue reports it; when several do... you get one separate series per venue') and the venue/stage catalogue is repeated from the schema. Some sentences do not fully earn their place, so it is adequate but not tight.

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 fully documents the return shapes (single series object and the multi-venue series array), the grain/unit fields, the rules block, and worked examples. Nothing an agent needs to call it correctly 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?

Schema coverage is already 100%, so baseline is 3, but the description adds real semantics: which stages each venue reports, the defaulted 'registered' stage, and the rule that omitting venue yields one series per reporting venue. It complements the schema rather than merely restating it.

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 states a specific verb+resource with scope ('whether a measurement is going up or down') and explicitly names the siblings it is not (onchain_agent_get_agent_economy, onchain_agent_get_listing_history). An agent can distinguish it from every other sibling 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 opens with 'USE WHEN', gives a 'NOT FOR' exclusion naming the correct alternative tools for each excluded case, and provides four concrete example utterances mapping to calls. When-to-use and when-not-to-use are both explicit.

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

All Sato Hub: Build Onchain & Crypto Agents 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