Skip to main content
Glama

Read an immutable ERC-8004 validation document

tereno_erc8004_validation

Free. Lookup an on-chain evaluation attestation and signed EIP-712 proof by validation ID, returned with permanent content-addressed keccak256 ETag.

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": {
      "validationId": "<validationId>"
    },
    "name": "tereno_erc8004_validation"
  }
}

Input Schema

NameRequiredDescriptionDefault
validationIdYesValidation ID (e.g. val-...) or hash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses cost (free), immutability of the document, the content-addressed keccak256 ETag (implying cacheability/verification), and that the returned proof is EIP-712 signed. It omits error/miss behavior and any auth requirements, keeping it short of a 5.

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?

One dense sentence with no filler, and the 'Free' cost signal is front-loaded. The phrasing is jargon-heavy but every clause conveys a distinct fact about the call or its result.

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 one-parameter read tool with no output schema, the description usefully characterizes the return value (attestation plus signed EIP-712 proof plus ETag). Completeness is good; only failure modes and any auth expectations are unaddressed.

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 coverage is 100% and the single parameter is already documented as a 'val-...' ID or hash. The description only restates 'by validation ID' and adds no format, casing, or fallback detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Lookup') and specific resource ('on-chain evaluation attestation and signed EIP-712 proof') keyed by validation ID, so the agent knows exactly what it retrieves. It does not differentiate against any sibling, but the resource is narrow enough that confusion is unlikely.

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?

Usage is only implied: an agent infers it should call this when it already has a validation ID and wants the attestation. 'Free' signals no credit cost, which is a useful call-freely hint, but there is no explicit when-to-use vs. alternative or prerequisite guidance.

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.