Synthex Forge — x402 Paid Agent Services

Create Control Proof

create_control_proof

Destructive

Proof that a claimer controls an identifier, signed and dated. use it rather than create_dispute_ruling for control proof, not dispute ruling; an object with 30 fields including algorithm, attestedAt. $0.2 USDC.

Input Schema

Name	Required	Description
`claimer`	No	The claimer this operation operates on. See the schema for its type and whether it is required.
`identifier`	No	The identifier this operation operates on. See the schema for its type and whether it is required.
`control_method`	No	The control method this operation operates on. See the schema for its type and whether it is required.
`control_evidence`	No	The control evidence this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`noKyc`	No	The `noKyc` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`schema`	No	The `schema` field of the response.
`sha256`	No	The `sha256` field of the response.
`claimer`	No	The `claimer` field of the response.
`receipt`	No	The `receipt` field of the response.
`signals`	No	The `signals` field of the response.
`verdict`	Yes	The decision this tool returned.
`claimsAt`	No	The `claimsAt` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`typedCore`	No	The `typedCore` field of the response.
`verify_at`	No	The `verify_at` field of the response.
`attestedAt`	No	The `attestedAt` field of the response.
`disclaimer`	No	The `disclaimer` field of the response.
`identifier`	No	The `identifier` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`signals_list`	No	The `signals_list` field of the response.
`controlMethod`	No	The `controlMethod` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`controlBoundary`	No	The `controlBoundary` field of the response.
`controlEvidence`	No	The `controlEvidence` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`nonDeterminative`	No	The `nonDeterminative` field of the response.
`verificationHint`	No	The `verificationHint` field of the response.
`notIdentityDetermination`	No	The `notIdentityDetermination` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed32 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / attestedAt

Added value: +{
+  "description": "The `attestedAt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / canonicalSha256

Added value: +{
+  "description": "The `canonicalSha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / claimer

Added value: +{
+  "description": "The `claimer` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / claimsAt

Added value: +{
+  "description": "The `claimsAt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / controlBoundary

Added value: +{
+  "description": "The `controlBoundary` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / controlEvidence

Added value: +{
+  "description": "The `controlEvidence` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / controlMethod

Added value: +{
+  "description": "The `controlMethod` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / disclaimer

Added value: +{
+  "description": "The `disclaimer` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / identifier

Added value: +{
+  "description": "The `identifier` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "The `kind` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / noKyc

Added value: +{
+  "description": "The `noKyc` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / nonDeterminative

Added value: +{
+  "description": "The `nonDeterminative` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / notIdentityDetermination

Added value: +{
+  "description": "The `notIdentityDetermination` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / observations

Added value: +{
+  "description": "The `observations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / publicKeyHex

Added value: +{
+  "description": "The `publicKeyHex` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "description": "The `receipt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / schema

Added value: +{
+  "description": "The `schema` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signals

Added value: +{
+  "description": "The `signals` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signals_list

Added value: +{
+  "description": "The `signals_list` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signature

Added value: +{
+  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
+  "type": "string"
+}

addedOutput schema / properties / signedBy

Added value: +{
+  "description": "The `signedBy` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / typedCore

Added value: +{
+  "description": "The `typedCore` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / verificationHint

Added value: +{
+  "description": "The `verificationHint` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verify_at

Added value: +{
+  "description": "The `verify_at` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "signature",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare the full safety profile (readOnly=false, idempotent=false, destructive=true, openWorld=false), so the bar is lower. The description adds real value by disclosing the paid cost ('$0.2 USDC') and the signed-and-dated nature of the artifact. However, it never reconciles the destructiveHint=true annotation — an agent cannot tell what persistent state is written or overwritten by this 'create' operation.

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?

Three short fragments, front-loaded with the artifact definition and then the routing rule and cost. It is efficient, but the phrasing is telegraphic ('an object with 30 fields including algorithm, attestedAt') and the cost sentence sits oddly at the end rather than near the routing decision.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile. What remains unaddressed is the destructiveHint=true behavior and any persistence/payment-flow preconditions for a $0.2 USDC write operation, which is a meaningful gap for a mutating tool.

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 carries parameter documentation and the baseline of 3 applies. The description adds no parameter-level meaning (no explanation of claimer, identifier, control_method, or control_evidence), so it neither helps nor hurts beyond the schema.

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 names the resource precisely ('proof that a claimer controls an identifier, signed and dated') and the tool's verb is carried by the name 'create_control_proof'. It explicitly differentiates from the closest sibling, create_dispute_ruling, so an agent can separate the two without opening schemas.

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?

It gives an explicit routing rule: 'use it rather than create_dispute_ruling for control proof, not dispute ruling.' That is a concrete when-to-use/when-not signal, though only one alternative is addressed despite a large sibling set of other create_*/issue_* attestation tools.

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

All Synthex Forge — x402 Paid Agent Services tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.