Synthex Forge — x402 Paid Agent Services

Assess Market Regime

assess_market_regime

Read-onlyIdempotent

Return ONE signed, dated regime read. use it rather than assess_portfolio_risk for market regime, not portfolio risk; an object with 28 fields including adx, as_of. $0.05 USDC.

Input Schema

Name	Required	Description	Default
`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.
`method`	No	The method this operation operates on. See the schema for its type and whether it is required.	combined
`series`	No	The time series the operation reads.

Output Schema

Name	Required	Description
`adx`	No	The `adx` field of the response.
`bars`	No	The `bars` field of the response.
`kind`	No	The `kind` field of the response.
`as_of`	No	The date the answer is computed as of.
`slope`	No	The `slope` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`method`	No	The `method` field of the response.
`regime`	No	The `regime` field of the response.
`atr_pct`	No	The `atr_pct` field of the response.
`reasons`	No	The `reasons` field of the response.
`features`	No	The `features` field of the response.
`raw_slope`	No	The `raw_slope` 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.
`confidence`	No	Confidence in the verdict, 0 to 1.
`public_key`	No	The `public_key` field of the response.
`methodology`	No	The `methodology` field of the response.
`realised_vol`	No	The `realised_vol` field of the response.
`coverage_gaps`	No	The `coverage_gaps` 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.
`profile_version`	No	Version of the answer profile.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`minimum_required`	No	The `minimum_required` field of the response.
`recent_vol_ratio`	No	The `recent_vol_ratio` field of the response.
`methodology_version`	No	Version of the method that produced the answer.
`signature_algorithm`	No	The `signature_algorithm` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 31, 2026

addedOutput schema / properties / kind

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

addedOutput schema / properties / methodology

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

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

Changed26 schema fields changedOct 31, 2026

addedOutput schema / properties / adx

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

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

addedOutput schema / properties / bars

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

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

addedOutput schema / properties / coverage_gaps

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

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

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

addedOutput schema / properties / minimum_required

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

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

addedOutput schema / properties / raw_slope

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

addedOutput schema / properties / realised_vol

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

addedOutput schema / properties / reasons

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

addedOutput schema / properties / recent_vol_ratio

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

addedOutput schema / properties / regime

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

addedOutput schema / properties / slope

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

removedOutput schema / properties / status

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond annotations: the result is signed, dated, a single regime read, includes 28 fields such as `adx` and `as_of`, and costs $0.05 USDC. It does not discuss auth or rate limits, but the cost and signed-output disclosure is substantive.

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

Conciseness5/5

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

The description is short and front-loaded: purpose first, sibling differentiation second, output/cost details last. Every phrase carries useful selection or invocation information, with no filler.

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

Completeness5/5

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

Given an output schema, annotations, and 100% schema coverage, the description supplies the remaining decision-relevant details: it is a single signed/dated regime read, distinct from portfolio risk, with a known field count and price. Nothing critical for correct selection or invocation appears missing.

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 parameters are already documented in the schema, and the description does not add meaning for `method` or `series`. Its mention of `as_of` is framed as an output field rather than explaining the parameter's reproducibility behavior beyond what the schema already states.

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

Purpose5/5

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

The description gives a specific verb and resource — "Return ONE signed, dated regime read" — and explicitly distinguishes it from `assess_portfolio_risk`. An agent can identify it as a market-regime assessment rather than a portfolio-risk tool without opening either schema.

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 explicitly says to use this rather than `assess_portfolio_risk` for market regime, not portfolio risk, giving a clear alternative and scope condition. It does not address other market-data siblings such as `get_market_snapshot` or `get_market_history`, so the routing guidance is clear but not exhaustive.

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.