Classification Receipt & Appeal Layer

verify_attestation

Verify a per-request function attestation

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": {
      "agent_id": "<agent_id>",
      "function": "<function>",
      "url": "<url>",
      "sig": "<sig>"
    },
    "name": "verify_attestation"
  }
}

Input Schema

Name	Required	Description	Default
`ts`	No
`sig`	Yes
`url`	Yes
`agent_id`	Yes
`function`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

D1.8/5.0

Behavior1/5

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

With no annotations provided, the description carries the full behavioral-disclosure burden, and it discloses nothing: no indication of what verification entails, whether it is read-only, what happens on failure, or what the caller receives. The single sentence adds no behavioral context beyond the tool name.

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

Conciseness2/5

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

The description is a single short sentence with no wasted words, but the brevity comes from under-specification rather than efficiency. Critical context is missing rather than compressed.

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

Completeness1/5

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

For a tool with five parameters (four required), no annotations, no output schema, and no schema descriptions, the description is completely inadequate. An agent cannot determine parameter meaning, verification semantics, or expected outcomes from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Five parameters (agent_id, function, url, sig, ts) exist with 0% schema description coverage, yet the description never mentions any of them. It provides no explanation of what 'sig', 'ts', or the attestation fields represent or how they are used.

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

Purpose3/5

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

The description has a specific verb ('Verify') and a resource ('per-request function attestation'), but the resource is jargon that an agent may not be able to interpret without prior context. It makes no attempt to distinguish this from the sibling 'verify_receipt', which likely handles an adjacent verification concept.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over 'verify_receipt' or any other sibling, and no stated prerequisites or exclusions. The agent is left to infer usage entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Classification Receipt & Appeal Layer tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?