Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

Sync a copy of the directory

onchain_agent_get_changes
Read-onlyIdempotent

USE WHEN you keep a local copy of the directory and need only what moved since your last sync (machine-readable added / updated / removed), rather than re-fetching the whole catalog. NOT FOR a readable headline feed or one project's history (use onchain_agent_recent_changes instead), or the current state of one record (use onchain_agent_get_resource).

RETURNS (json): what changed since a given date: additions, per-resource change events, and retirements. { since, until, window_days, next_since, counts:{added,changed,updated,removed,material}, added:[...], changed:[{slug,name,url,events:[...]}], updated:[{slug,name,url,changed_fields,material,material_fields}], removed:[...], coverage:{...}, full_export }.

CURSOR: next_since is the date to pass as since on your next call. It starts the next window at a snapshot taken before this read, so a change cannot fall between two calls; it overlaps by a couple of days, so dedupe by slug. To watch a fixed list of listings, call on a schedule with since = the last next_since and look for your slugs in each lane. A call with no argument returns a truncated sample: take the cursor from a call with since or detail "full", not from the sample.

COVERAGE (also stated in the response): added is exact. updated is a field-level diff of every catalog field between the snapshot on baseline_date and the live record — complete at daily resolution, so a quiet copy edit IS caught. changed is the richer event log (score moves, releases, verification) and explains WHY. removed is approximate. Mirror from added + updated + removed. Read-only.

MATERIAL: each updated row also carries material (true/false) and material_fields; counts.material counts them. A move in the uptime window, a re-stamped check date, a star or success-rate move inside its band, or a score move under the threshold is not material. To watch for real changes only, pass only: "material" (the answer says it was filtered); a mirror keeps the default.

WITH NO since (and no detail: "full") the answer is compact, labelled rule "defaulted": exact counts for the default 14-day window and the newest rows of each lane (summary: true, shown, omitted, order, example_calls). It is a sample, not a sync. Pass since (any date) or detail: "full" for every row; a later since is a shorter window and a smaller answer. All free.

Examples:

  • "what moved recently" -> {} (compact) · every row -> { detail: "full" }

  • "what's new this week" -> { since: "2026-08-23" }

  • "sync my copy" or "watch my list" -> { since: }

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_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNo'material' lists only the `updated` rows whose change is material (not just the uptime window, a re-stamped reading date, a star or success-rate move inside its band, a score move under the threshold); the answer carries `filter` saying so. Default 'all': every changed row, for a mirror.
sinceNoReturn everything that changed since this ISO date. Defaults to 14 days ago. Clamped to the 90-day supported window.
detailNo'full' returns the whole feed for the default 14-day window even with no `since`. Omitted with no `since`, the answer is compact: exact counts for the window plus the newest rows of each lane, and the exact calls for the rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / only
      Added value: +{
      +  "description": "'material' lists only the `updated` rows whose change is material (not just the uptime window, a re-stamped reading date, a star or success-rate move inside its band, a score move under the threshold); the answer carries `filter` saying so. Default 'all': every changed row, for a mirror.",
      +  "enum": [
      +    "all",
      +    "material"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "'full' returns the whole feed for the default 14-day window even with no `since`. Omitted with no `since`, the answer is compact: exact counts for the window plus the newest rows of each lane, and the exact calls for the rest.",
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
  3. 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"
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial behavior the annotations cannot convey: the `next_since` cursor starts a snapshot overlapping by a couple of days so callers must dedupe by slug, an argument-less call returns a truncated sample that must not be used as a sync cursor, and coverage is asymmetric (added exact, updated complete at daily resolution, removed approximate). These are exactly the operational traits an agent would otherwise get wrong.

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?

Front-loaded USE WHEN / NOT FOR / RETURNS / CURSOR / COVERAGE / MATERIAL sections make it scannable despite its length, and the examples close with actionable argument sketches. It is on the verbose side and contains some admitted duplication ('COVERAGE (also stated in the response)') plus a throwaway line ('All free.'), which costs a point but does not obscure the content.

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 response envelope keys (since, until, counts, added, changed, updated, removed, coverage, full_export) and by disclosing the default/no-argument truncation behavior with its `summary/shown/omitted` flags. For a zero-required-parameter sync tool, an agent has everything needed to call it correctly and to interpret the result.

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 100%, so the baseline would be 3; the description earns above baseline by explaining how `since` is meant to be sourced (the `next_since` of the previous call) and how `only: "material"` interacts with the mirror use case, including that a mirror should keep the default. It does not restate the 90-day clamp or the enum values beyond what the schema already gives.

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 opens with a specific verb-and-resource statement ('only what moved since your last sync ... machine-readable added / updated / removed, rather than re-fetching the whole catalog'), which pins down both scope and output shape. It then explicitly separates itself from onchain_agent_recent_changes (human-readable headline feed) and onchain_agent_get_resource (single-record state), so an agent can disambiguate without opening any 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?

Explicit USE WHEN and NOT FOR clauses name both alternatives and the conditions that select them, and the examples map natural-language intents ('what moved recently', 'sync my copy', 'watch my list') onto concrete argument sets. The only gap is that 'steer to recent_changes' is stated but the boundary case (mixed need) is not addressed, which is minor.

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.