Skip to main content
Glama

Ellimist

Signed point-in-time snapshot

data_attest_snapshot
Read-only

Signed statement of the value Ellimist recorded at or just before time T: Aave USDC rates, native USDC supply or the Treasury curve. For backtests, audits and disputes. Price: $0.01 USDC per call via x402 (no account). Not charged if it fails.

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": {
      "feed": "<feed>",
      "key": "<key>",
      "at": "<at>"
    },
    "name": "data_attest_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesPoint in time (UTC) to attest
keyYesChain (base, ethereum) or UST
feedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds meaningful operational context: pricing at $0.01 USDC per call via x402, no account required, and no charge on failure. It does not explain signature verification or response format, but it covers key behavioral traits for a paid read-only attestation.

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

Conciseness5/5

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

The description is three tight sentences, front-loading the core attestation concept, then use cases, then pricing. Every sentence contributes useful selection or invocation context without unnecessary detail.

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?

For a three-parameter read-only tool with no output schema, the description sufficiently explains the signed statement concept, supported feeds, use cases, and billing behavior. It could be richer about the returned signed artifact, but it is adequate for correct tool selection and invocation.

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?

The description clarifies the 'at' semantics as 'recorded at or just before time T' and restates the feed options in plain language, which adds some meaning beyond the enum. However, it does not explain the 'key' parameter or how chain identifiers interact with each feed, leaving part of the schema to carry the load.

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 artifact and scope: a signed statement of a value recorded at or just before time T, covering Aave USDC rates, native USDC supply, or the Treasury curve. This distinguishes it from live-data siblings by emphasizing the signed, point-in-time attestation purpose.

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?

The description gives explicit use cases such as backtests, audits, and disputes, which clearly signals when this tool is appropriate. It does not name when-not-to-use cases or alternative tools by name, so it falls short of the top score.

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