Synthex Forge — x402 Paid Agent Services

Create Provenance Overlay

create_provenance_overlay

Destructive

Produce a signed provenance overlay for a piece of content. use it rather than create_a2a_escrow for provenance overlay, not a2a escrow; an object with 27 fields including canonicalization, chain_depth. $0.1 USDC.

Input Schema

Name	Required	Description
`creator`	No	The creator this operation operates on. See the schema for its type and whether it is required.
`sources`	No	The sources this operation operates on. See the schema for its type and whether it is required.
`content_sha256`	No	The content sha256 this operation operates on. See the schema for its type and whether it is required.
`transformations`	No	The transformations this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`uri`	No	The `uri` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`detail`	Yes	Human-readable explanation of the verdict.
`creator`	No	The `creator` field of the response.
`sources`	No	The `sources` field of the response.
`verdict`	Yes	The decision this tool returned.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_by`	No	The key id that signed the answer.
`chain_depth`	No	The `chain_depth` field of the response.
`retrieved_at`	No	The `retrieved_at` field of the response.
`evidence_core`	Yes	The canonical, signed core of the answer — the payload the signature covers.
`hash_verified`	No	The `hash_verified` field of the response.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`scopeBoundary`	No	The `scopeBoundary` field of the response.
`content_sha256`	No	The `content_sha256` field of the response.
`missing_fields`	No	The `missing_fields` field of the response.
`profileVersion`	No	Version of the answer profile.
`scope_boundary`	No	What this service explicitly does not do.
`overlay_version`	No	The `overlay_version` field of the response.
`profile_version`	No	Version of the answer profile.
`transformations`	No	The `transformations` field of the response.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`verified_sources`	No	The `verified_sources` field of the response.
`methodologyVersion`	No	The `methodologyVersion` field of the response.
`unverified_sources`	No	The `unverified_sources` field of the response.
`methodology_version`	No	Version of the method that produced the answer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedOct 31, 2026

addedOutput schema / properties / canonicalization

Added value: +{
+  "description": "The canonicalisation rule the digest was computed under.",
+  "type": "string"
+}

addedOutput schema / properties / chain_depth

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

addedOutput schema / properties / content_sha256

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

addedOutput schema / properties / creator

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / evidence_core

Added value: +{
+  "description": "The canonical, signed core of the answer — the payload the signature covers.",
+  "type": "object"
+}

addedOutput schema / properties / hash_verified

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / methodologyVersion

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

addedOutput schema / properties / methodology_version

Added value: +{
+  "description": "Version of the method that produced the answer.",
+  "type": "string"
+}

addedOutput schema / properties / missing_fields

Added value: +{
+  "description": "The `missing_fields` 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 / output_sha256

Added value: +{
+  "description": "SHA-256 hex digest of the canonical evidence core.",
+  "type": "string"
+}

addedOutput schema / properties / overlay_version

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

addedOutput schema / properties / profileVersion

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / profile_version

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / retrieved_at

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

addedOutput schema / properties / scopeBoundary

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

addedOutput schema / properties / scope_boundary

Added value: +{
+  "description": "What this service explicitly does not do.",
+  "type": "string"
+}

addedOutput schema / properties / signature

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

addedOutput schema / properties / signed_by

Added value: +{
+  "description": "The key id that signed the answer.",
+  "type": "string"
+}

addedOutput schema / properties / sources

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

removedOutput schema / properties / status

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

addedOutput schema / properties / transformations

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

addedOutput schema / properties / unverified_sources

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

addedOutput schema / properties / uri

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / verified_sources

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description adds real context beyond the annotations: the output is signed, it is a paid call ('$0.1 USDC'), and it relates to provenance/canonicalization. But annotations declare destructiveHint=true and idempotentHint=false, and the description never explains what is destroyed or whether a retry creates a duplicate — a notable gap for a mutation tool.

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

Conciseness3/5

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

The purpose is front-loaded, but the second sentence is garbled and partially redundant ('use it rather than create_a2a_escrow for provenance overlay, not a2a escrow'). The '27 fields including canonicalization, chain_depth' clause repeats information a caller already gets from the output schema.

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, describing return fields is unnecessary, and what remains leaves gaps: it does not say what signing/credential requirements exist, why the tool is flagged destructive, or what the content_sha256 is expected to identify. Adequate for a simple 4-parameter create, but thin for a destructive, paid mutation.

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 four parameters (creator, sources, content_sha256, transformations) are already documented in the schema. The description mentions 'canonicalization' and 'chain_depth', but those are output fields, not parameters, so it adds no meaning for inputs. 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?

The first sentence states a specific verb ('Produce') and resource ('signed provenance overlay for a piece of content'), and the second sentence explicitly distinguishes it from create_a2a_escrow. The phrasing is muddled ('use it rather than ... for provenance overlay, not a2a escrow') but an agent can still tell what it does and what it is not.

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 names an explicit alternative, create_a2a_escrow, and says this tool is for provenance overlays, not a2a escrow. That is a clear routing rule, though there are no exclusions or preconditions beyond the one contrast.

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.