Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

How fresh is the data behind each answer

onchain_agent_get_data_freshness
Read-onlyIdempotent

USE WHEN you are about to quote a Sato Hub number, score, count or feed item and want to know how old it is — or when a figure looks stale and you need to know whether the pipeline behind it is late. NOT FOR how a number is measured (use onchain_agent_explain_number instead) or what changed in the directory (use onchain_agent_recent_changes).

COVERS, per data surface (directory activity, news, Sato Score, liveness checks, snapshots, ERC-8004 counts, the weekly agent-economy measurements, x402, LP pools, skills, deploy verification and more): when it was last collected successfully, when a collection was last attempted and how that ended, how often it is expected to run, whether it is late, the next scheduled run, and the ledger step it was read from.

RULE ENFORCED: late = now − last success > 1.5 × the expected cadence (daily 36h, weekly 252h). A surface built from several pipeline steps is as fresh as its stalest step, and one of its steps never succeeding makes it late. A surface on time whose newest successful run read only part of its data is state: "partial" (partial: true), never "fresh": what it did not read is unknown, not zero. A surface with no recorded success at all returns last_success_at: null and late: null — unknown, never an invented date. If the ledger cannot be read, every surface is unknown, never "fresh". A late surface still serves its last good data: quote it WITH its date.

RETURNS (json): { generated_at, ledger, rule, surfaces: [{ surface, what, expected_every, last_success_at, last_attempt_at, last_status, late, partial, state, age_hours, late_after_hours, next_update, source, steps: [{ step, last_success_at, partial, last_attempt_at, last_status }], served_by }], note, source_url, sato_url }. Timestamps and statuses of data jobs only — no usage figures. Read-only.

Example: { surface: "sato_score" }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "onchain_agent_get_data_freshness"
  }
}

Input Schema

NameRequiredDescriptionDefault
surfaceNoOne data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, erc8004_agents_celo, custody_profiles, sato_scan, sato_scan_census, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, custody_observed, dead_project_sweep.
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. Changed2 schema fields changed
    • changedInput schema / properties / surface / description
      Previous value: -"One data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, custody_profiles, sato_scan, sato_scan_census, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, custody_observed, dead_project_sweep."New value: +"One data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, erc8004_agents_celo, custody_profiles, sato_scan, sato_scan_census, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, custody_observed, dead_project_sweep."
    • changedInput schema / properties / surface / enum
      Previous value: -[
      -  "directory_activity",
      -  "news",
      -  "erc8004_count",
      -  "agent_tokens",
      -  "liveness",
      -  "sato_score",
      -  "snapshots",
      -  "x402_bazaar",
      -  "x402_answers_daily",
      -  "erc8004_endpoints_daily",
      -  "mcp_alive_daily",
      -  "erc8004_router_pool",
      -  "passports",
      -  "erc8004_census",
      -  "x402_throughput",
      -  "custody_profiles",
      -  "sato_scan",
      -  "sato_scan_census",
      -  "agent_economy",
      -  "x402_settlement",
      -  "lp_pools",
      -  "skills",
      -  "deploy_verification",
      -  "custody_observed",
      -  "dead_project_sweep"
      -]New value: +[
      +  "directory_activity",
      +  "news",
      +  "erc8004_count",
      +  "agent_tokens",
      +  "liveness",
      +  "sato_score",
      +  "snapshots",
      +  "x402_bazaar",
      +  "x402_answers_daily",
      +  "erc8004_endpoints_daily",
      +  "mcp_alive_daily",
      +  "erc8004_router_pool",
      +  "passports",
      +  "erc8004_census",
      +  "x402_throughput",
      +  "erc8004_agents_celo",
      +  "custody_profiles",
      +  "sato_scan",
      +  "sato_scan_census",
      +  "agent_economy",
      +  "x402_settlement",
      +  "lp_pools",
      +  "skills",
      +  "deploy_verification",
      +  "custody_observed",
      +  "dead_project_sweep"
      +]
  3. 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."
  4. Changed2 schema fields changed
    • changedInput schema / properties / surface / description
      Previous value: -"One data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, custody_profiles, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, custody_observed, dead_project_sweep."New value: +"One data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, custody_profiles, sato_scan, sato_scan_census, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, custody_observed, dead_project_sweep."
    • changedInput schema / properties / surface / enum
      Previous value: -[
      -  "directory_activity",
      -  "news",
      -  "erc8004_count",
      -  "agent_tokens",
      -  "liveness",
      -  "sato_score",
      -  "snapshots",
      -  "x402_bazaar",
      -  "x402_answers_daily",
      -  "erc8004_endpoints_daily",
      -  "mcp_alive_daily",
      -  "erc8004_router_pool",
      -  "passports",
      -  "erc8004_census",
      -  "x402_throughput",
      -  "custody_profiles",
      -  "agent_economy",
      -  "x402_settlement",
      -  "lp_pools",
      -  "skills",
      -  "deploy_verification",
      -  "custody_observed",
      -  "dead_project_sweep"
      -]New value: +[
      +  "directory_activity",
      +  "news",
      +  "erc8004_count",
      +  "agent_tokens",
      +  "liveness",
      +  "sato_score",
      +  "snapshots",
      +  "x402_bazaar",
      +  "x402_answers_daily",
      +  "erc8004_endpoints_daily",
      +  "mcp_alive_daily",
      +  "erc8004_router_pool",
      +  "passports",
      +  "erc8004_census",
      +  "x402_throughput",
      +  "custody_profiles",
      +  "sato_scan",
      +  "sato_scan_census",
      +  "agent_economy",
      +  "x402_settlement",
      +  "lp_pools",
      +  "skills",
      +  "deploy_verification",
      +  "custody_observed",
      +  "dead_project_sweep"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / surface / description
      Previous value: -"One data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, dead_project_sweep."New value: +"One data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, custody_profiles, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, custody_observed, dead_project_sweep."
    • changedInput schema / properties / surface / enum
      Previous value: -[
      -  "directory_activity",
      -  "news",
      -  "erc8004_count",
      -  "agent_tokens",
      -  "liveness",
      -  "sato_score",
      -  "snapshots",
      -  "x402_bazaar",
      -  "x402_answers_daily",
      -  "erc8004_endpoints_daily",
      -  "mcp_alive_daily",
      -  "erc8004_router_pool",
      -  "passports",
      -  "erc8004_census",
      -  "x402_throughput",
      -  "agent_economy",
      -  "x402_settlement",
      -  "lp_pools",
      -  "skills",
      -  "deploy_verification",
      -  "dead_project_sweep"
      -]New value: +[
      +  "directory_activity",
      +  "news",
      +  "erc8004_count",
      +  "agent_tokens",
      +  "liveness",
      +  "sato_score",
      +  "snapshots",
      +  "x402_bazaar",
      +  "x402_answers_daily",
      +  "erc8004_endpoints_daily",
      +  "mcp_alive_daily",
      +  "erc8004_router_pool",
      +  "passports",
      +  "erc8004_census",
      +  "x402_throughput",
      +  "custody_profiles",
      +  "agent_economy",
      +  "x402_settlement",
      +  "lp_pools",
      +  "skills",
      +  "deploy_verification",
      +  "custody_observed",
      +  "dead_project_sweep"
      +]
  6. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: it defines the lateness rule (1.5x cadence, 36h/252h), explains that a surface is as fresh as its stalest step, that partial reads yield state=partial rather than fresh, that missing successes return null rather than an invented date, and that an unreadable ledger yields unknown. Minor remaining gap: it doesn't say how the response is scoped when surface is omitted beyond the schema.

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?

Dense but well structured with USE WHEN / NOT FOR / COVERS / RULE / RETURNS headings and a concrete example, so it is front-loaded and scannable. The COVERS paragraph and parts of the RETURNS field list partially restate the enum values and schema, costing some length.

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?

There is no output schema, and the description compensates fully by enumerating the returned JSON shape (surfaces, steps, late, partial, state, age_hours, late_after_hours, served_by). Combined with the enforcement rule, null/unknown semantics and read-only note, an agent has everything needed to call and interpret it.

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% and the surface enum is fully documented, so the schema carries the parameter burden. The description loosely enumerates surfaces in human-readable form ("Sato Score", "ERC-8004 counts") which only partly bridges to the snake_case enum values, and response_format is not discussed at all. Baseline 3.

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?

States a specific verb and resource: report how old the data behind a Sato Hub figure is, per data surface, including lateness and partiality. It explicitly separates itself from onchain_agent_explain_number (how a number is measured) and onchain_agent_recent_changes (what changed), so an agent can pick it without opening the 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?

Opens with an explicit USE WHEN trigger (about to quote a number, or a figure looks stale) and a NOT FOR block naming two sibling tools and the condition that selects each. Nothing is left to inference.

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.