Skip to main content
Glama
sebastienrousseau

iso20022-evidence-pack-mcp

Sign an evidence pack

sign_pack
Read-onlyIdempotent

Sign the canonical JSON content of an evidence pack using the server's Ed25519 private key to produce a detached signature, public key, and key ID. Returns an error if no signing key is configured.

Instructions

Sign a pack's canonical content with the server's Ed25519 key.

The private key is configured by the operator via the environment (see
:mod:`iso20022_evidence_pack_mcp.signing`); it never crosses the tool
boundary. Returns the detached signature, the public key, and a key id;
fails with ``EP_NO_SIGNING_KEY`` when no key is configured.

Args:
    pack_content: The evidence pack to sign, as JSON text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pack_contentYesAn evidence pack as raw JSON text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context: the private key is configured via environment, never crosses boundary, returns detached signature/public key/key id, and fails with EP_NO_SIGNING_KEY. No contradiction with annotations.

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 concise, with a clear one-line summary, followed by essential operational details. No extraneous sentences. The Args section is well-structured.

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?

For a simple tool with one parameter, strong annotations, and an output schema, the description covers key aspects: key configuration, return values, error condition. It is fully adequate for the agent.

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 the single parameter. The description repeats that pack_content is 'the evidence pack to sign, as JSON text', which adds minimal value over the schema's description. Baseline 3 is appropriate.

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?

The description uses the specific verb 'Sign' and identifies the resource as 'a pack's canonical content'. It clearly distinguishes from sibling tools like 'verify_pack_signature' and 'seal_pack' by focusing on the signing operation.

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?

The description implicitly places signing as part of a workflow (after building, before sealing) but does not explicitly state when not to use this tool or mention alternatives. However, the sibling context aids differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/iso20022-evidence-pack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server