Skip to main content
Glama

Default-watch and pinning service

verify_attestation

Verify a signed effective-default attestation (forged/tampered attestations return valid: false)

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": {
      "attestation": "<attestation>"
    },
    "name": "verify_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
attestationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one valuable behavioral trait: invalid attestations return valid: false instead of raising an error, so the agent knows to inspect the payload rather than catch exceptions. It does not state whether verification is read-only, what auth or trust root is required, or what else the response contains.

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?

A single front-loaded sentence with zero filler; the parenthetical adds non-obvious outcome semantics rather than restating the name.

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

Completeness2/5

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

For a tool whose only parameter is a nested free-form object and which has no output schema, the description must define the input shape and the return payload. It only reveals that the result carries a valid boolean for tampered inputs, leaving the agent unable to construct a correct attestation argument.

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

Parameters2/5

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

There is a single required parameter typed only as a generic object with 0% schema description coverage, and the description says nothing about its required fields (signature, payload, key id, etc.). The word 'signed' hints at a signature component but leaves the structure undocumented in both schema and description.

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 (verify) and resource (signed attestation), and clarifies the outcome semantics for forged/tampered inputs. 'Effective-default attestation' is domain jargon the agent may not resolve, but the operation itself is unambiguous and siblings do not overlap.

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 implied by the name and description — call it when you need to check an attestation's signature. There is no explicit when/when-not guidance or mention of prerequisites, though no sibling competes for this role, so the omission is tolerable rather than harmful.

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