Skip to main content
Glama

Attify

Verify an Attify attestation

verify_attestation
Read-onlyIdempotent

Checks an attestation's Ed25519 signature against Attify's published keys, then whether it is still current: a vendor verification (not superseded, expired or revoked) or a traction report (not expired or withdrawn). Give the attestation JSON as published, or a vendor attestation's id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
attestationNoThe attestation: {"payload": {...}, "signature": {...}}.
attestation_idNoAn attestation id, e.g. "att_…".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real substance: the cryptographic check performed, the key source, and the specific invalidation conditions (superseded, expired, revoked for vendor attestations; expired, withdrawn for traction reports). The remaining gap is what happens on failure — an error versus a negative result — which is left unstated.

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?

Two sentences, front-loaded with the primary verification action, with the acceptance modes in the second. The parenthetical lists of invalidation states are dense but each item earns its place; there is no filler or restatement of the title.

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

Completeness3/5

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

For a verification tool with no output schema, the description says nothing about the shape of the result — whether it returns a boolean, a status object, or per-check details — which is the main thing an agent needs to consume the call. It also omits error behavior for a malformed signature or unknown id, though the input-side coverage is otherwise solid.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the two parameters are alternatives rather than cumulative, and the id form is only valid for vendor attestations. It does not say explicitly that exactly one must be supplied, which is the one unclosed ambiguity for a tool with zero required parameters.

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?

Names a specific verb (checks) and a precisely scoped resource (an attestation's Ed25519 signature against Attify's published keys), then adds a second stage — currency checking — with the two attestation kinds enumerated (vendor verification vs traction report). An agent knows exactly what this tool does and that it is not a general lookup like lookup_vendor or get_evidence.

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 closing clause gives the two accepted input modes ('the attestation JSON as published, or a vendor attestation's id'), which is useful invocation guidance, but there is no explicit statement of when to reach for this tool versus siblings like get_verdict or explain_provenance, and no exclusions. Usage is implied by the tool's purpose rather than stated.

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