Skip to main content
Glama

Aevum: verified trading records

Re-check a grade

recheck_certificate
Read-only

Independently re-grade a certificate: fetches the public prices (Atlas on-chain, Coinbase candles, or Kraken trades), applies the locked rule with the grader's own open code, and compares with what Aevum recorded on Ethereum. Returns match / mismatch / unsupported with each step. Takes a few seconds (up to ~30 s for long target/stop calls). Anyone can run the same check in their browser on the certificate page.

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": {
      "id": "<id>"
    },
    "name": "recheck_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCertificate id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing latency ('a few seconds, up to ~30 s for long target/stop calls'), the external data sources consulted (Atlas on-chain, Coinbase candles, Kraken trades), and the outcome vocabulary (match / mismatch / unsupported with each step). That is exactly the behavioral context an agent needs before committing to a possibly slow call.

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?

Three sentences, front-loaded with the action, then mechanism, then cost and fallback. Dense but every clause earns its place — no restatement of the tool name or filler.

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?

With no output schema, the description correctly takes on the burden of describing return values (match/mismatch/unsupported per step) and timing, which makes it callable with confidence. Minor gap: it doesn't say what happens on error or whether results are cached/repeatable.

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?

There is a single parameter with 100% schema coverage and an inline description ('Certificate id'), so the schema already carries the meaning. The description adds nothing further about the id, which is acceptable at this coverage level but not value-adding.

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 precise verb and resource ('Independently re-grade a certificate') and spells out the mechanism: fetching public prices, applying the locked rule with the grader's own open code, and comparing against what was recorded on Ethereum. This is clearly distinct from a plain fetch like get_certificate.

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

Usage Guidelines3/5

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

The framing ('Independently re-grade', 'Anyone can run the same check') implies the verification use case, but it never states explicitly when to choose this over simply retrieving the certificate, nor any preconditions or exclusions. Usage is inferable rather than spelled out.

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