Skip to main content
Glama
zkproofport

zkproofport-ai

by zkproofport
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

submit_proof

Step 3 of the step-by-step flow: Submit prepared inputs to generate the ZK proof. The TEE server runs the Noir circuit and returns the UltraHonk proof. This step may take 30-90 seconds. The TEE server builds Prover.toml from these inputs.

Instructions

Step 3 of the step-by-step flow: Submit prepared inputs to generate the ZK proof. The TEE server runs the Noir circuit and returns the UltraHonk proof. This step may take 30-90 seconds. The TEE server builds Prover.toml from these inputs.

You MUST pass the nonce returned by request_challenge. POST /api/v1/prove answers every request that arrives without that nonce with a fresh 402 challenge, so a submission that omits it can never produce a proof.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nonceYesThe "nonce" field from the request_challenge response. Single-use and bound to the circuit it was issued for — request a new challenge for every submission and for every circuit.
inputsNoFull ProveInputs object from prepare_inputs. Accepts a JSON string or a structured object.
circuitYesWhich circuit to use
prepared_inputs_idNoPrivate local action witness handle returned by prepare_inputs. Use instead of inputs; consumed once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.46
    • changedInput schema / properties / circuit / enum
      Previous value: -[
-  "coinbase_kyc",
-  "coinbase_country",
-  "oidc_domain",
-  "arc_eligibility",
-  "giwa_attestation"
-]New value: +[
+  "coinbase_kyc",
+  "coinbase_country",
+  "oidc_domain",
+  "giwa_attestation"
+]
  2. Changed2 schema fields changedv0.2.45
    • addedInput schema / properties / prepared_inputs_id
      Added value: +{
+  "description": "Private local action witness handle returned by prepare_inputs. Use instead of inputs; consumed once.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "circuit",
-  "inputs",
-  "nonce"
-]New value: +[
+  "circuit",
+  "nonce"
+]
  3. Changed1 schema field changedv0.2.44
    • changedInput schema / properties / circuit / enum
      Previous value: -[
-  "coinbase_kyc",
-  "coinbase_country",
-  "oidc_domain",
-  "arc_eligibility"
-]New value: +[
+  "coinbase_kyc",
+  "coinbase_country",
+  "oidc_domain",
+  "arc_eligibility",
+  "giwa_attestation"
+]
  4. Changed3 schema fields changedv0.2.43
    • changedInput schema / properties / circuit / enum
      Previous value: -[
-  "coinbase_kyc",
-  "coinbase_country",
-  "oidc_domain"
-]New value: +[
+  "coinbase_kyc",
+  "coinbase_country",
+  "oidc_domain",
+  "arc_eligibility"
+]
    • addedInput schema / properties / nonce
      Added value: +{
+  "description": "The \"nonce\" field from the request_challenge response. Single-use and bound to the circuit it was issued for — request a new challenge for every submission and for every circuit.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "circuit",
-  "inputs"
-]New value: +[
+  "circuit",
+  "inputs",
+  "nonce"
+]
  5. First observedv0.2.9

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses latency (30-90s), server-side behavior (TEE runs the Noir circuit, builds Prover.toml, returns an UltraHonk proof), and the failure mode when the nonce is omitted (402). It does not cover other error handling or retry semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the flow step and outcome, then the nonce constraint. Both paragraphs earn their place, though the second paragraph is somewhat repetitive in stressing the nonce.

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?

With no output schema, the description usefully states what is returned (UltraHonk proof) and how long it takes, and it flags the mandatory nonce dependency. It is largely complete, missing only broader failure/retry context.

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 description coverage is 100%, so the schema already documents nonce single-use binding, the circuit enum, inputs formats, and prepared_inputs_id. The description reinforces the nonce requirement but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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 and resource ('Submit prepared inputs to generate the ZK proof') and positions itself as step 3 of the flow, so an agent can place it. However, it never distinguishes itself from the sibling generate_proof, which a reader could easily confuse with this tool.

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 flow-step framing ('Step 3') plus the explicit dependency on a nonce from request_challenge and inputs from prepare_inputs gives clear when-to-use context. It stops short of stating exclusions or when to prefer an alternative such as generate_proof.

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

Deploy Server

Other Tools