Skip to main content
Glama

Change history and feed (paid)

get_change_records
Read-onlyIdempotent

Past and recent changes as records, for monitoring a position or auditing a contract's history: the change history as record/v1 records, oldest first: what changed, from what to what, who acted, who may execute or revoke it, when it takes effect, and the transaction and log each rests on. With address, one contract's history; without, the feed across every covered contract (filter with since, a block number). Paged: pass the previous result's next_cursor. Paid per call over x402; a call without a payment returns the price and where to buy, and charges nothing.

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": "get_change_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
sinceNoFirst Ethereum block to include (default 0).
cursorNo
familyNoFeed only: a family id from get_coverage, e.g. metamorpho-v1.1.
addressNoOptional: only this contract's records.
observed_statusNoA record's status as first observed; a record never changes, so what is pending now is get_control_state's `pending`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the bar is low, yet the description adds substantial operational context: oldest-first ordering, cursor pagination ('pass the previous result's next_cursor'), and a per-call x402 payment model where an unpaid call returns the price and where to buy and charges nothing. The payment/auth behavior is exactly the kind of disclosure annotations cannot express.

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 and front-loaded: scope, then payload, then the address/feed split, then paging and payment. Slightly repetitive in the opening ('Past and recent changes as records... the change history as record/v1 records'), but every subsequent clause carries information an agent needs to call correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Strong for a 7-parameter, no-output-schema tool: it describes return contents, ordering, pagination, and the payment fallback, which substitutes for a missing output schema. The gap is `kind` (change/action/bundle), which has no explanation in either the description or the schema, so an agent must guess what record types it selects.

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?

Adds real meaning beyond the schema for `address` (whole-contract scope vs. global feed) and `cursor` (feed it the previous result's next_cursor, which the schema only implies via a regex pattern). `since` is restated as a block number, matching the schema, and `family`, `kind`, and `observed_status` are left to the schema's own descriptions.

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 — returns past and recent changes as record/v1 records, oldest first — and enumerates the payload ('what changed, from what to what, who acted, who may execute or revoke it, when it takes effect'). It also distinguishes the two scopes: 'With `address`, one contract's history; without, the feed across every covered contract.'

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

Usage Guidelines4/5

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

Frames the use cases explicitly ('monitoring a position or auditing a contract's history') and gives the scoping decision rule via `address` vs. the global feed. It even disambiguates against get_control_state by noting that a record never changes, so currently-pending items belong there. It stops short of naming an alternative for status-based lookups outright.

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.

Resources