Synthex Forge — x402 Paid Agent Services

Create Attested Financial Evidence

create_attested_financial_evidence

Destructive

Signed, dated financial evidence. use it rather than create_code_review_brief for attested financial evidence, not code review brief; an object with 26 fields including algorithm, balanceSheetIdentity. $0.35 USDC.

Input Schema

Name	Required	Description
`period`	No	The reporting period the answer covers.
`company`	No	The company this operation operates on. See the schema for its type and whether it is required.
`statement`	No	The statement this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`low`	No	The `low` field of the response.
`high`	No	The `high` field of the response.
`note`	No	A note on how the answer was produced.
`flags`	No	The `flags` field of the response.
`label`	No	The `label` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`medium`	No	The `medium` field of the response.
`period`	No	The `period` field of the response.
`sha256`	No	The `sha256` field of the response.
`company`	No	The `company` field of the response.
`metrics`	No	The `metrics` field of the response.
`verdict`	Yes	The decision this tool returned.
`evidence`	No	The `evidence` field of the response.
`severity`	No	The `severity` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`missingFields`	No	The `missingFields` field of the response.
`providedFields`	No	The `providedFields` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`figuresProvided`	No	The `figuresProvided` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`balanceSheetIdentity`	No	The `balanceSheetIdentity` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / balanceSheetIdentity

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / company

Added value: +{
+  "description": "The `company` field of the response.",
+  "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 / evidence

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

addedOutput schema / properties / figuresProvided

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

addedOutput schema / properties / flags

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

addedOutput schema / properties / high

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

addedOutput schema / properties / label

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

addedOutput schema / properties / low

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

addedOutput schema / properties / medium

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

addedOutput schema / properties / metrics

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

addedOutput schema / properties / missingFields

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

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

addedOutput schema / properties / providedFields

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / severity

Added value: +{
+  "description": "The `severity` 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"
+}

removedOutput schema / properties / status

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

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

A3.5/5.0

Behavior4/5

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

Annotations already declare the safety profile (not read-only, destructive, non-idempotent, closed-world), and the description adds context beyond them: the evidence is signed and dated, the output is an object with 26 fields including algorithm and balanceSheetIdentity, and each call costs $0.35 USDC. It does not explain why a 'create' operation carries destructiveHint=true, which is the one behavioral question left open.

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 and front-loads the resource description, but the clause 'for attested financial evidence, not code review brief' redundantly repeats the tool name and the alternative already named a few words earlier. The fragments make it compact but not cleanly structured.

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 explained, and annotations cover safety, leaving little burden on the description. However, with zero required parameters (all defaulting to empty strings) and a per-call price plus destructive flag, an agent would benefit from knowing which inputs actually matter and what the signing/attestation step entails — neither is covered.

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 period, company and statement; baseline 3 applies. The description's field mentions (algorithm, balanceSheetIdentity) refer to the output object, not the three inputs, so it adds no meaning to the parameters.

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 identifies the resource ('signed, dated financial evidence') and explicitly contrasts it with the sibling `create_code_review_brief`, so an agent can route between the two without opening either schema. It falls short of a 5 because it is a noun fragment with the verb only implied by the name, and the phrasing ('for attested financial evidence, not code review brief') is garbled.

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 names one explicit alternative and the condition that selects this tool over it, which is real routing guidance. But it only addresses one of many near-identical siblings (create_audit_evidence_package, issue_attestation, create_signed_data_snapshot, create_signed_research_brief), and gives no when-not-to-use guidance.

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.