Synthex Forge — x402 Paid Agent Services

Get Market Snapshot

get_market_snapshot

Read-onlyIdempotent

A point-in-time market snapshot for an instrument. use it rather than assess_market_regime for market snapshot, not market regime; an object with 54 fields including 15M, 1D. $0.01 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.
`limit`	No	Maximum number of items to return.
`to_ts`	No	The to ts this operation operates on. See the schema for its type and whether it is required.
`from_ts`	No	The from ts this operation operates on. See the schema for its type and whether it is required.
`instrument`	No	The market instrument the operation concerns.
`granularity`	No	The granularity this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`1D`	No	The `1D` field of the response.
`1H`	No	The `1H` field of the response.
`1M`	No	The `1M` field of the response.
`1W`	No	The `1W` field of the response.
`4H`	No	The `4H` field of the response.
`5M`	No	The `5M` field of the response.
`ok`	Yes	Whether the operation succeeded.
`to`	No	The `to` field of the response.
`15M`	No	The `15M` field of the response.
`30M`	No	The `30M` field of the response.
`60M`	No	The `60M` field of the response.
`DAY`	No	The `DAY` field of the response.
`MIN`	No	The `MIN` field of the response.
`HOUR`	No	The `HOUR` field of the response.
`WEEK`	No	The `WEEK` field of the response.
`asOf`	No	The `asOf` field of the response.
`bars`	No	The `bars` field of the response.
`from`	No	The `from` field of the response.
`note`	No	A note on how the answer was produced.
`DAILY`	No	The `DAILY` field of the response.
`as_of`	No	The date the answer is computed as of.
`limit`	No	The `limit` field of the response.
`notes`	No	The `notes` field of the response.
`HOURLY`	No	The `HOURLY` field of the response.
`MINUTE`	No	The `MINUTE` field of the response.
`WEEKLY`	No	The `WEEKLY` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`reason`	No	Why the verdict was reached.
`sha256`	No	The `sha256` field of the response.
`MINUTES`	No	The `MINUTES` field of the response.
`lastBar`	No	The `lastBar` field of the response.
`verdict`	Yes	The decision this tool returned.
`firstBar`	No	The `firstBar` field of the response.
`last_bar`	No	The `last_bar` field of the response.
`rowCount`	No	The `rowCount` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`first_bar`	No	The `first_bar` field of the response.
`row_count`	No	The `row_count` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`instrument`	No	The `instrument` field of the response.
`sourceHash`	No	The `sourceHash` field of the response.
`granularity`	No	The `granularity` field of the response.
`source_hash`	No	The `source_hash` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`sourceHashIs`	No	The `sourceHashIs` field of the response.
`storeVersion`	No	The `storeVersion` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`store_version`	No	The `store_version` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`expectedBarCount`	No	The `expectedBarCount` field of the response.
`expected_bar_count`	No	The `expected_bar_count` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed56 schema fields changedOct 31, 2026

addedOutput schema / properties / 15M

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

addedOutput schema / properties / 1D

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

addedOutput schema / properties / 1H

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

addedOutput schema / properties / 1M

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

addedOutput schema / properties / 1W

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

addedOutput schema / properties / 30M

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

addedOutput schema / properties / 4H

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

addedOutput schema / properties / 5M

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

addedOutput schema / properties / 60M

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

addedOutput schema / properties / DAILY

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

addedOutput schema / properties / DAY

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

addedOutput schema / properties / HOUR

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

addedOutput schema / properties / HOURLY

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

addedOutput schema / properties / MIN

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

addedOutput schema / properties / MINUTE

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

addedOutput schema / properties / MINUTES

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

addedOutput schema / properties / WEEK

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

addedOutput schema / properties / WEEKLY

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / asOf

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

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

addedOutput schema / properties / canonicalSha256

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

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

addedOutput schema / properties / expectedBarCount

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

addedOutput schema / properties / expected_bar_count

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

addedOutput schema / properties / firstBar

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

addedOutput schema / properties / first_bar

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

addedOutput schema / properties / from

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

addedOutput schema / properties / granularity

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

addedOutput schema / properties / instrument

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

addedOutput schema / properties / lastBar

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

addedOutput schema / properties / last_bar

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

addedOutput schema / properties / limit

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

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

addedOutput schema / properties / ok

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / rowCount

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

addedOutput schema / properties / row_count

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

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

addedOutput schema / properties / sourceHashIs

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

addedOutput schema / properties / source_hash

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

removedOutput schema / properties / status

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

addedOutput schema / properties / storeVersion

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

addedOutput schema / properties / store_version

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

addedOutput schema / properties / to

Added value: +{
+  "description": "The `to` 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",
+  "ok",
+  "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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: a price of $0.01 USDC per call and a hint about response shape (54 fields including 15M, 1D). It does not mention rate limits or whether the snapshot is cached, but the paid-call disclosure is the important behavioral fact.

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?

Three short sentences, front-loaded with the purpose. The middle clause ('for market snapshot, not market regime') is redundant with the preceding clause and reads awkwardly, but nothing else is wasted.

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 return values need not be enumerated; the description still adds field-count and interval hints plus pricing. The main gap is that all six parameters are optional and the description does nothing to clarify default behavior beyond what the schema states.

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 baseline is 3 even though several schema descriptions are boilerplate ('The to ts this operation operates on'). The description adds no parameter meaning beyond the schema — notably it never explains granularity or how from_ts/to_ts interact with as_of.

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?

States a specific verb and resource ('point-in-time market snapshot for an instrument') and explicitly names the sibling it is not (assess_market_regime for 'market regime'). An agent can distinguish the two 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?

Names one concrete alternative and the condition that selects it ('use it rather than assess_market_regime'). It gives no guidance on when to prefer get_market_history or get_market_history_bulk, which are the closest data-retrieval siblings, so routing is clear but incomplete.

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.