Synthex Forge — x402 Paid Agent Services

Create Signed Data Snapshot

create_signed_data_snapshot

Destructive

Signed Snapshot. use it rather than create_attested_financial_evidence for signed data snapshot, not attested financial evidence; an object with 36 fields including age_seconds, agedSeconds. $0.3 USDC.

Input Schema

Name	Required	Description
`series`	No	The time series the operation reads.
`sources`	No	The sources this operation operates on. See the schema for its type and whether it is required.
`subject`	No	The subject the operation is applied to — an id, a URL or a name, depending on the operation.
`fetched_at`	No	The fetched at this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`url`	No	The `url` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`tier`	No	The `tier` field of the response.
`title`	No	The `title` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`series`	No	The `series` field of the response.
`sha256`	No	The `sha256` field of the response.
`framing`	No	The `framing` field of the response.
`metrics`	No	The `metrics` field of the response.
`sources`	No	The `sources` field of the response.
`subject`	No	The `subject` field of the response.
`verdict`	Yes	The decision this tool returned.
`coverage`	No	How much of the underlying corpus the answer is based on.
`sealedAt`	No	The `sealedAt` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`fetchedAt`	No	The `fetchedAt` field of the response.
`freshness`	No	The `freshness` field of the response.
`publisher`	No	The `publisher` field of the response.
`row_count`	No	The `row_count` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`age_seconds`	No	The `age_seconds` field of the response.
`agedSeconds`	No	The `agedSeconds` field of the response.
`retrievedAt`	No	The `retrievedAt` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`skipped_rows`	No	The `skipped_rows` field of the response.
`source_count`	No	The `source_count` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`evidenceDigest`	No	The `evidenceDigest` field of the response.
`freshness_tier`	No	The `freshness_tier` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`skipped_sources`	No	The `skipped_sources` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed38 schema fields changedOct 31, 2026

addedOutput schema / properties / age_seconds

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

addedOutput schema / properties / agedSeconds

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / coverage

Added value: +{
+  "description": "How much of the underlying corpus the answer is based on.",
+  "type": "object"
+}

addedOutput schema / properties / detail

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

addedOutput schema / properties / ed25519Sig

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

addedOutput schema / properties / evidenceCore

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

addedOutput schema / properties / evidenceDigest

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

addedOutput schema / properties / fetchedAt

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

addedOutput schema / properties / framing

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

addedOutput schema / properties / freshness

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

addedOutput schema / properties / freshness_tier

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / metrics

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

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / retrievedAt

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

addedOutput schema / properties / row_count

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

addedOutput schema / properties / sealedAt

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

addedOutput schema / properties / series

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

addedOutput schema / properties / sha256

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

addedOutput schema / properties / signedBy

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

addedOutput schema / properties / skipped_rows

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

addedOutput schema / properties / skipped_sources

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

addedOutput schema / properties / source_count

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

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 / subject

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

addedOutput schema / properties / tier

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

addedOutput schema / properties / title

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

addedOutput schema / properties / url

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / verdictLevel

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds genuinely useful context the annotations lack: the price ($0.3 USDC) and the rough return shape (36 fields, age_seconds, agedSeconds). However, for a tool flagged destructive it never says what state is destroyed or whether the operation is reversible, which is the most important behavioral gap.

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?

It is short, but the middle clause is garbled and repetitive ("signed data snapshot, not attested financial evidence"), and the useful facts — output shape and price — trail behind the redundant routing phrase. Front-loading the cost/return facts would have made it tighter.

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?

An output schema exists, so return values need not be spelled out, and the schema fully documents the inputs. What is missing is what an agent most needs for a destructive, paid, non-idempotent call: what the snapshot covers and what the destructive side effect actually is.

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% across all four parameters (series, sources, subject, fetched_at), so the schema carries parameter meaning. The description adds nothing about any of them, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ("signed data snapshot") and contrasts it with a sibling, but the verb never appears and the phrase "signed data snapshot, not attested financial evidence" largely restates the tool name. It is enough to distinguish it from create_attested_financial_evidence, but not enough to say concretely what operation is performed.

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

Usage Guidelines3/5

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

It gives one explicit routing rule: prefer this over `create_attested_financial_evidence`. That names an alternative and a condition, which is real guidance, but there is no positive statement of when this tool is the right choice and no mention of the many other near-neighbours (create_signed_research_brief, create_x402_anchor, issue_attestation).

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.