Skip to main content
Glama

Verify envelope integrity (public)

verify_envelope

No key needed. Returns status, sealed-document hashes, certificate hash and audit-chain verification for an envelope id. Never returns document content.

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": {
      "envelope_id": "<envelope_id>"
    },
    "name": "verify_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
envelope_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description does useful work: it discloses that authentication is not required, lists the verification artifacts returned, and states that document content is never returned. It does not discuss rate limits, error behavior, or whether the operation is strictly read-only, so it is not fully exhaustive.

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?

The description is three short sentences, front-loads the access condition, then the return contents and privacy boundary. Every sentence adds relevant information with no filler.

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 simple one-parameter public verification tool, the description covers the key access and privacy behavior and names the returned artifacts. Because there is no output schema and no annotations, it is still somewhat thin on how envelope_id is obtained/formatted and how to interpret the returned status and hashes.

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?

The only parameter is envelope_id, and the schema provides no description coverage. The description merely restates 'for an envelope id' and does not add format, source, or validation guidance beyond the schema's name and maxLength constraint.

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 states a specific resource (an envelope id) and a concrete result set: status, sealed-document hashes, certificate hash, and audit-chain verification. It also distinguishes the call from content-returning envelope access by saying it never returns document content, though it does not explicitly name a sibling alternative.

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 description implies when to use it by noting that no key is needed and that it is a verification-only, non-content call. It does not explicitly say when to choose verify_envelope over get_envelope, get_audit_trail, or other sibling tools.

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