Skip to main content
Glama

zk_proof_get

Retrieve a ZK-SNARK proof for a specific trade, returning the Groth16 proof, public signals, and verification key for verification.

Instructions

Retrieve a ZK-SNARK proof for a specific trade. Returns the Groth16 proof, public signals, and verification key.

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

Input Schema

NameRequiredDescriptionDefault
trade_idYesTrade or order ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does usefully disclose the return payload (Groth16 proof, public signals, verification key), but says nothing about whether proof generation is expensive/slow, what happens when no proof exists for the trade, or whether any authorization is required.

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 sentences, front-loaded with the action and scope, then the return payload. Nothing is redundant or padded.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, describing the return contents is the main thing an agent needs and it is present. Minor gaps remain around failure modes and the relationship to the verification sibling.

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 with 100% schema description coverage, so the schema already documents trade_id. The description adds little beyond confirming the identifier refers to a trade whose proof is being fetched, matching the baseline for fully-covered schemas.

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?

States a specific verb ('Retrieve') and resource ('ZK-SNARK proof') scoped to a single trade, and enumerates the payload returned. It does not explicitly contrast itself with the sibling zk_proof_verify, so the differentiation relies on the reader inferring retrieval vs. verification.

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?

The phrase 'for a specific trade' implies the input context but there is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g., proof must already exist), and no pointer to zk_proof_verify as the follow-up step.

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