Synthex Forge — x402 Paid Agent Services

Run Monte Carlo

run_monte_carlo

Read-onlyIdempotent

Return ONE signed, dated Monte Carlo distribution. use it rather than assess_market_regime for monte carlo, not market regime; an object with 28 fields including as_of, canonicalization. $0.15 USDC.

Input Schema

Name	Required	Description
`runs`	No	The runs this operation operates on. See the schema for its type and whether it is required.
`seed`	No	The random seed, so a stochastic answer can be reproduced exactly.
`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.
`trades`	No	The trades this operation operates on. See the schema for its type and whether it is required.
`trade_distribution`	No	The trade distribution this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`p5`	No	The `p5` field of the response.
`p25`	No	The `p25` field of the response.
`p50`	No	The `p50` field of the response.
`p75`	No	The `p75` field of the response.
`p95`	No	The `p95` field of the response.
`runs`	No	The `runs` field of the response.
`seed`	No	The `seed` field of the response.
`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.
`method`	No	The `method` field of the response.
`trades`	No	The `trades` field of the response.
`reasons`	No	The `reasons` field of the response.
`verdict`	Yes	The decision this tool returned.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_by`	No	The key id that signed the answer.
`public_key`	No	The `public_key` field of the response.
`method_note`	No	The `method_note` field of the response.
`percentiles`	No	The `percentiles` field of the response.
`prob_profit`	No	The `prob_profit` 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.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`max_drawdown_p50`	No	The `max_drawdown_p50` field of the response.
`max_drawdown_p95`	No	The `max_drawdown_p95` field of the response.
`risk_per_trade_pct`	No	The `risk_per_trade_pct` field of the response.
`signature_algorithm`	No	The `signature_algorithm` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed30 schema fields changedOct 31, 2026

addedOutput schema / properties / as_of

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

addedOutput schema / properties / canonicalization

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

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

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

addedOutput schema / properties / max_drawdown_p50

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

addedOutput schema / properties / max_drawdown_p95

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

addedOutput schema / properties / method

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

addedOutput schema / properties / method_note

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

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

addedOutput schema / properties / p5

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

addedOutput schema / properties / p50

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

addedOutput schema / properties / p75

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

addedOutput schema / properties / p95

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

addedOutput schema / properties / percentiles

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

addedOutput schema / properties / prob_profit

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

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

addedOutput schema / properties / runs

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

addedOutput schema / properties / seed

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

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

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value beyond them: the output is signed and dated, carries 28 fields including as_of and canonicalization, and the call costs $0.15 USDC — the cost disclosure is especially useful for an agent budgeting spend.

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?

Purpose is front-loaded and the whole thing is short, but the middle clause is syntactically confusing and the price ('$0.15 USDC.') hangs as an unintegrated fragment with a stray period. Brevity is undercut by awkward wording rather than by excess length.

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 needn't be explained, and the schema covers all inputs. However, for a paid, deterministic simulation with a nested `trade_distribution` object, the description says nothing about what the distribution should contain or how payment/billing is invoked, leaving the highest-stakes parts of the call unexplained.

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% and every parameter (runs, seed, as_of, trades, trade_distribution) is documented in the schema, so baseline 3 applies. The description mentions `as_of` only as an output field, not as an input lever for reproducing a past answer, so it adds no parameter meaning beyond the schema.

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 and resource: 'Return ONE signed, dated Monte Carlo distribution,' and names the sibling it must not be confused with. The phrasing is slightly garbled ('for monte carlo, not market regime') but an agent can still distinguish this from assess_market_regime and assess_risk_of_ruin at a glance.

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: use this rather than `assess_market_regime` when the task is Monte Carlo, and not when the task is market regime. That is a concrete alternative-and-condition statement, though it only covers one sibling out of many risk-assessment tools and gives no explicit when-not conditions beyond that single contrast.

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.