Skip to main content
Glama

verify_and_sign

Verifies a numerical claim and returns a locally signed Ed25519 receipt proving data integrity and issuer identity, not input truth.

Instructions

Check a numerical claim and issue a locally signed Ed25519 receipt. The signature proves integrity and local issuer identity, not the truth of supplied inputs.

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": {
      "request": "<request>"
    },
    "name": "verify_and_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does deliver a genuinely useful caveat: the signature proves integrity and local issuer identity but not the truth of inputs. However, it omits whether the receipt is persisted or returned only, whether signing requires a configured key or permissions, and any idempotency or side-effect information.

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 tight sentences, front-loaded with the action and followed by the most decision-relevant caveat. No filler, repetition, or self-restatement of the tool name.

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

Completeness2/5

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

The presence of an output schema excuses explaining return values, but the combination of a completely undocumented nested request object and no annotations makes the definition too thin for correct invocation. The agent can understand the intent but not how to call it.

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?

Schema description coverage is 0% and the single parameter is an open nested object with additionalProperties=true, so the agent has no idea which fields (claim, expression, key id, etc.) to place in `request`. The description adds nothing about the shape or required content of that object, leaving a serious gap for a nested, undocumented input.

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 gives two specific verbs (check, issue) tied to concrete resources: a numerical claim and an Ed25519 receipt. That clearly separates it from siblings like check_signed_receipt or get_public_key, though the description never names those alternatives explicitly.

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 is only implied: an agent can infer it should call this when it needs both verification and a signed receipt. There is no explicit when-to-use/when-not-to-use guidance relative to verify_batch, verify_calculation, or check_signed_receipt, and no stated prerequisites.

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