Skip to main content
Glama

signafAIde

Verify a signafAIde verification pack

signafaide_verify_pack
Read-only

Use this when the user has a signafAIde verification pack (pack.json, written by signafaide export or downloaded through an auditor link) and wants it checked. Give the pack as JSON text in pack, or as an attached file in pack_file. The customer's agent keys (agent-keys.json) and signed head (head.json) are optional and are given the same way; without agent keys the client signature check cannot be independent and fails, as it does in the command-line verifier. The pack is checked against this service's own public signing keys, never against the keys inside the pack. Returns one line for each of the 12 checks (pass, pending, not checked or fail, naming the records that fail), tool coverage notes and a last line that starts with PASS or FAIL. Public timestamps are not looked up online: where a check would need that, it is reported as not checked. The pack is read in memory and is not stored; nothing is changed. The result is evidence about the records, not a certification. Inputs over 10 MB are refused.

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_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
headNoOptional. The customer's signed head as JSON text: the whole content of head.json (their .signafaide/head.json). With it, a pack with records cut from its end fails.
packNoThe verification pack as JSON text: the whole content of pack.json.
head_fileNoOptional. The customer's signed head as an attached file (head.json), in place of head.
pack_fileNoThe verification pack as an attached file (pack.json), in place of pack.
agent_keysNoOptional. The customer's agent keys as JSON text: the whole content of agent-keys.json, written by `signafaide keys export`.
agent_keys_fileNoOptional. The customer's agent keys as an attached file (agent-keys.json), in place of agent_keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only and non-destructive, but the description adds substantial behavior: 12 named checks, the pass/pending/not-checked/fail vocabulary, no online timestamp lookup, in-memory processing with nothing stored, and the trust model (pack checked against the service's keys, not keys inside the pack). It also discloses the 10 MB refusal limit and that missing agent keys cause the signature check to fail.

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?

Front-loaded with the usage trigger, then input modes, then return shape and limits. Dense but nearly every sentence carries distinct information; a few clauses (e.g. repeating the JSON-text/attached-file pairing already in the schema) could be trimmed.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so precisely: one line per check, coverage notes, and a final PASS/FAIL line. Combined with the trust model, storage behavior, and size limit, an agent has everything needed to call it and interpret results.

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%, so the schema already documents all six parameters including the JSON-text vs attached-file pairing. The description adds one genuinely new consequence not in the schema — that omitting agent keys makes the client signature check non-independent and failing, and that head enables truncation detection — but otherwise restates what the schema says, so baseline 3 applies.

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?

States a specific verb and resource ('verify a signafAIde verification pack') and immediately identifies the artifact (pack.json written by `signafaide export` or from an auditor link), which separates it from siblings like signafaide_check_auditor_link and signafaide_service_keys.

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

Usage Guidelines4/5

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

Gives a clear trigger condition ('when the user has a verification pack ... and wants it checked') and explains the two ways to supply each input. It does not explicitly say when to prefer a sibling or when not to use this tool, so it stops short of full routing 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.

Resources