Synthex Forge — x402 Paid Agent Services

Create Synthesis Verdict

create_synthesis_verdict

Destructive

Fold research + quant + audit inputs into ONE signed verdict. use it rather than create_fund_tearsheet for synthesis verdict, not fund tearsheet; an object with 48 fields including agree, algorithm. $0.5 USDC.

Input Schema

Name	Required	Description
`audit`	No	The audit this operation operates on. See the schema for its type and whether it is required.
`quant`	No	The quant 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.
`research`	No	The research this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`area`	No	The `area` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`agree`	No	The `agree` field of the response.
`topic`	No	The `topic` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sha256`	No	The `sha256` field of the response.
`stance`	No	The `stance` field of the response.
`symbol`	No	The `symbol` field of the response.
`bearish`	No	The `bearish` field of the response.
`bullish`	No	The `bullish` field of the response.
`finding`	No	The `finding` field of the response.
`framing`	No	The `framing` field of the response.
`metrics`	No	The `metrics` field of the response.
`neutral`	No	The `neutral` field of the response.
`outcome`	No	The `outcome` field of the response.
`subject`	No	The `subject` field of the response.
`unknown`	No	The `unknown` field of the response.
`verdict`	Yes	The decision this tool returned.
`coverage`	No	How much of the underlying corpus the answer is based on.
`disagree`	No	The `disagree` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`strength`	No	The `strength` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`alignment`	No	The `alignment` field of the response.
`direction`	No	The `direction` field of the response.
`confidence`	No	Confidence in the verdict, 0 to 1.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`audit_fails`	No	The `audit_fails` field of the response.
`audit_warns`	No	The `audit_warns` field of the response.
`audit_passes`	No	The `audit_passes` 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.
`verdictLevel`	No	The `verdictLevel` field of the response.
`audit_entries`	No	The `audit_entries` field of the response.
`quant_entries`	No	The `quant_entries` field of the response.
`synthesizedAt`	No	The `synthesizedAt` field of the response.
`evidenceDigest`	No	The `evidenceDigest` field of the response.
`synthesisScore`	No	The `synthesisScore` field of the response.
`audit_pass_rate`	No	The `audit_pass_rate` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`research_entries`	No	The `research_entries` field of the response.
`blocks_with_signal`	No	The `blocks_with_signal` field of the response.
`synthesisDirection`	No	The `synthesisDirection` field of the response.
`quant_mean_strength`	No	The `quant_mean_strength` field of the response.
`research_mean_confidence`	No	The `research_mean_confidence` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed50 schema fields changedOct 31, 2026

addedOutput schema / properties / agree

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / alignment

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

addedOutput schema / properties / area

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

addedOutput schema / properties / audit_entries

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

addedOutput schema / properties / audit_fails

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

addedOutput schema / properties / audit_pass_rate

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

addedOutput schema / properties / audit_passes

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

addedOutput schema / properties / audit_warns

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

addedOutput schema / properties / bearish

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

addedOutput schema / properties / blocks_with_signal

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

addedOutput schema / properties / bullish

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / confidence

Added value: +{
+  "description": "Confidence in the verdict, 0 to 1.",
+  "type": "number"
+}

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

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

addedOutput schema / properties / disagree

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

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

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

addedOutput schema / properties / framing

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

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

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / quant_entries

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

addedOutput schema / properties / quant_mean_strength

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / research_entries

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

addedOutput schema / properties / research_mean_confidence

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

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

removedOutput schema / properties / status

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

addedOutput schema / properties / strength

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

addedOutput schema / properties / subject

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

addedOutput schema / properties / symbol

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

addedOutput schema / properties / synthesisDirection

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

addedOutput schema / properties / synthesisScore

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

addedOutput schema / properties / synthesizedAt

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

addedOutput schema / properties / topic

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

addedOutput schema / properties / unknown

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

A3.5/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, but the description never explains why this is destructive or what side effects occur. It does add real value not in annotations: the $0.5 USDC cost and the shape of the output (48 fields including agree, algorithm).

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?

Front-loaded purpose is good and it is short, but the middle clause repeats the sibling name twice and reads as a stitched-together instruction, wasting part of an otherwise tight description.

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?

Output schema exists, so return detail is optional (though the 48-field mention is a bonus). However, for a destructive, non-idempotent operation, the description omits why it mutates state and any prerequisites for the paid call beyond the price.

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 coverage is 100%, so the four parameters are already documented. The description maps the three input groups (research, quant, audit) but says nothing about the 'subject' parameter or item-level formats; baseline 3 applies since the schema carries the detail.

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 ('Fold') and a concrete resource ('research + quant + audit inputs into ONE signed verdict'), and names the sibling it is not (create_fund_tearsheet). The garbled phrasing ('use it rather than ... for synthesis verdict, not fund tearsheet') slightly muddies an otherwise clear purpose.

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?

Explicitly routes the agent away from the sibling: use this instead of create_fund_tearsheet for a synthesis verdict. The repetition of the same point twice is wasteful but the when-to-use guidance is unambiguous.

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.