Skip to main content
Glama

Verify the local signafAIde records

signafaide_verify

Verifies signed, tamper-evident records of AI agent tool calls by checking schemas, hashes, signatures, chain links, and Merkle proofs; returns PASS or FAIL per check.

Instructions

Checks every record in the project's .signafaide/ folder (or a verification pack): schema, hashes, agent signatures, chain links and content hashes, and, for records a witness has co-signed, Merkle proofs, the service's batch and head signatures, drand and anchors. With an API key it first ships waiting records; without one nothing is sent. Returns one line per check, what still needs the witness, and PASS or FAIL.

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": "signafaide_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNoPath of a pack from `signafaide export`, instead of the local state.
directoryNoPath of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does much of it: it discloses the conditional network side effect (uploading waiting records only when an API key is present), that verification is conditional for witness co-signed records, and what the output looks like (one line per check, pending witness items, PASS/FAIL). It does not say whether local files are modified during verification or whether the call can be slow on large projects.

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?

Structure is front-loaded: the verb and scope come first, then the enumerated checks, then the API-key side effect, then the return shape. The middle clause is a long list but each item is informative; minimal padding.

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?

There is no output schema, and the description compensates by describing the return ('one line per check, what still needs the witness, and PASS or FAIL'). Both optional parameters are covered by the schema, and the conditional side effect is disclosed. Complete enough for an agent to call it correctly, though a note on cost or idempotency would improve it.

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% for both parameters, so the baseline is 3. The description reinforces the pack-vs-directory relationship ('or a verification pack') and implies pack replaces local state, but that is essentially what the schema descriptions already state, so it adds little new meaning.

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?

The description names a specific verb ('Checks') and resource ('every record in the project's .signafaide/ folder'), then enumerates exactly what is checked: schema, hashes, agent signatures, chain links, content hashes, Merkle proofs, batch/head signatures, drand and anchors. That level of specificity leaves no ambiguity about what the tool does. It never contrasts itself with signafaide_status or the setup siblings, so it falls short of the top mark for sibling differentiation.

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 context is implied rather than stated: it covers a project folder or an exported pack, and it discloses the API-key condition ('With an API key it first ships waiting records; without one nothing is sent'). There is no explicit when-to-use versus when-to-use-something-else, e.g. no guidance on choosing this over signafaide_status for a quick health check.

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