Skip to main content
Glama

zk_proof_verify

Verifies a Groth16 ZK-SNARK proof server-side for a given trade or order ID and returns whether the proof is mathematically valid.

Instructions

Verify a ZK-SNARK proof server-side. Returns whether the Groth16 proof is mathematically valid.

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": {
      "trade_id": "<trade_id>"
    },
    "name": "zk_proof_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
trade_idYesTrade or order ID to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It reveals that verification happens server-side and yields a mathematical validity answer for Groth16, but it does not say whether the call mutates state (e.g. records a verification result), what happens when no proof exists for the trade, or whether failures surface as errors versus a false result.

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 short sentences, front-loaded with the action and followed by the return contract. Every phrase (server-side, Groth16, mathematically valid) adds precision and nothing is padded.

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 single-parameter tool without annotations, the description covers purpose and return semantics adequately, and there is no output schema to compensate for. It falls short on state-changing behavior, error conditions, and how the trade_id relates to proof availability, all of which matter for correct invocation.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already defines trade_id as the trade or order ID. The description adds no format, sourcing, or error semantics for that ID, and notably does not explain that supplying only an ID implies the proof is retrieved from server-side storage — a meaningful implicit behavior left unstated.

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?

Uses a specific verb plus resource ("Verify a ZK-SNARK proof") and narrows the proof system to Groth16, so the agent knows exactly what operation is performed. It does not, however, distinguish itself from siblings like zk_proof_get or verify_trace, which share the proof domain.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus zk_proof_get (fetch a proof) or verify_trace (verify a trace), nor any prerequisite such as the proof already being stored server-side. The only guidance is what the tool does, leaving the agent to infer selection criteria.

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