Synthex Forge — x402 Paid Agent Services

Assess Quant Overlap

assess_quant_overlap

Read-onlyIdempotent

Return ONE signed, dated overlap matrix. use it rather than assess_market_regime for quant overlap, not market regime; an object with 27 fields including a, as_of. $0.1 USDC.

Input Schema

Name	Required	Description
`as_of`	No	The date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
`threshold`	No	The threshold this operation operates on. See the schema for its type and whether it is required.
`strategies`	No	The strategies this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`a`	No	The `a` field of the response.
`b`	No	The `b` field of the response.
`id`	No	The `id` field of the response.
`corr`	No	The `corr` field of the response.
`note`	No	A note on how the answer was produced.
`as_of`	No	The date the answer is computed as of.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`matrix`	No	The `matrix` field of the response.
`reasons`	No	The `reasons` field of the response.
`returns`	No	The `returns` field of the response.
`verdict`	Yes	The decision this tool returned.
`clusters`	No	The `clusters` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_by`	No	The key id that signed the answer.
`threshold`	No	The `threshold` field of the response.
`public_key`	No	The `public_key` field of the response.
`observations`	No	The `observations` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`crowded_pairs`	No	The `crowded_pairs` field of the response.
`evidence_core`	Yes	The canonical, signed core of the answer — the payload the signature covers.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`pairs_measured`	No	The `pairs_measured` field of the response.
`strategy_count`	No	The `strategy_count` field of the response.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`insufficient_pairs`	No	The `insufficient_pairs` field of the response.
`signature_algorithm`	No	The `signature_algorithm` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedOct 31, 2026

addedOutput schema / properties / a

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

addedOutput schema / properties / as_of

Added value: +{
+  "description": "The date the answer is computed as of.",
+  "type": "string"
+}

addedOutput schema / properties / b

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

addedOutput schema / properties / canonicalization

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

addedOutput schema / properties / clusters

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

addedOutput schema / properties / corr

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

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / crowded_pairs

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

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

addedOutput schema / properties / insufficient_pairs

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

addedOutput schema / properties / key_id

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

addedOutput schema / properties / matrix

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

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

addedOutput schema / properties / pairs_measured

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

addedOutput schema / properties / public_key

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

addedOutput schema / properties / reasons

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

addedOutput schema / properties / returns

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

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

addedOutput schema / properties / signed_by

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

removedOutput schema / properties / status

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

addedOutput schema / properties / strategy_count

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

addedOutput schema / properties / threshold

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

addedOutput schema / properties / verdict

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new context: the result is signed and dated, a single matrix is returned, and the call costs $0.1 USDC — a payment trait no annotation conveys. It stops short of saying whether reproducibility depends on as_of or what 'signed' attests to.

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?

Compact and front-loaded: purpose first, then sibling routing, then output shape and price. The semicolon-clause 'an object with 27 fields including a, as_of' is awkward and truncated, slightly undercutting the structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the field enumeration is redundant but harmless; the cost disclosure and sibling routing are the pieces an agent actually needs. What 'overlap' measures and how threshold alters the matrix is left implicit, but the schema carries those parameters.

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 as_of, threshold, and strategies are already documented in the schema, including as_of's reproducibility use. The description mentions as_of only as an output field, adding nothing about threshold semantics or what strategies overlap is measured against. 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?

States a concrete verb and resource ('Return ONE signed, dated overlap matrix') and distinguishes itself from the sibling it is most likely confused with, assess_market_regime. The trailing 'including a, as_of' field list is garbled and adds noise rather than clarity.

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

Usage Guidelines5/5

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

Explicitly names the alternative (assess_market_regime) and the condition that selects this tool instead ('for quant overlap, not market regime'). An agent can route between the two without opening either schema.

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.