Synthex Forge — x402 Paid Agent Services

Get Market History

get_market_history

Read-onlyIdempotent

Signed bar series over an explicit range. use it rather than get_market_history_bulk for market history, not market history bulk; an object with 27 fields including allowlist, detail. $1 USDC.

Input Schema

Name	Required	Description	Default
`end`	No	The end this operation operates on. See the schema for its type and whether it is required.
`start`	No	The start this operation operates on. See the schema for its type and whether it is required.
`format`	No	The format this operation operates on. See the schema for its type and whether it is required.	json
`source`	No	The source this operation operates on. See the schema for its type and whether it is required.
`timeframe`	No	The timeframe this operation operates on. See the schema for its type and whether it is required.
`instrument`	No	The market instrument the operation concerns.

Output Schema

Name	Required	Description
`end`	No	The `end` field of the response.
`gaps`	No	The `gaps` field of the response.
`note`	No	A note on how the answer was produced.
`rows`	No	The `rows` field of the response.
`limit`	No	The `limit` field of the response.
`start`	No	The `start` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`series`	No	The `series` field of the response.
`sha256`	No	The `sha256` field of the response.
`source`	No	The `source` field of the response.
`last_ts`	No	The `last_ts` field of the response.
`licence`	No	The `licence` field of the response.
`verdict`	Yes	The decision this tool returned.
`first_ts`	No	The `first_ts` field of the response.
`manifest`	No	The `manifest` field of the response.
`allowlist`	No	The `allowlist` field of the response.
`permitted`	No	The `permitted` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`timeframe`	No	The `timeframe` field of the response.
`instrument`	No	The `instrument` field of the response.
`limit_days`	No	The `limit_days` field of the response.
`generated_at`	No	The `generated_at` field of the response.
`requested_bars`	No	The `requested_bars` field of the response.
`requested_days`	No	The `requested_days` field of the response.
`permitted_sources`	No	The `permitted_sources` field of the response.
`permitted_timeframes`	No	The `permitted_timeframes` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedOct 31, 2026

addedOutput schema / properties / allowlist

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

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / end

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

addedOutput schema / properties / first_ts

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

addedOutput schema / properties / gaps

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

addedOutput schema / properties / generated_at

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

addedOutput schema / properties / instrument

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

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

addedOutput schema / properties / licence

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

addedOutput schema / properties / limit

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

addedOutput schema / properties / limit_days

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

addedOutput schema / properties / manifest

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

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

addedOutput schema / properties / permitted_sources

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

addedOutput schema / properties / permitted_timeframes

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

addedOutput schema / properties / requested_bars

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

addedOutput schema / properties / requested_days

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

addedOutput schema / properties / rows

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

addedOutput schema / properties / series

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

addedOutput schema / properties / sha256

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

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

addedOutput schema / properties / start

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

removedOutput schema / properties / status

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

addedOutput schema / properties / timeframe

Added value: +{
+  "description": "The `timeframe` 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",
+  "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 read-only, idempotent, non-destructive behavior, and the description adds useful context beyond them: the output is a signed bar series, the response is an object with 27 fields including allowlist/detail, and the call costs $1 USDC. That pricing and signing context is genuinely valuable for invocation decisions.

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?

The description is short and front-loads the return shape, but the sibling distinction is worded redundantly ('for market history, not market history bulk') and the '27 fields' detail may be unnecessary given an output schema exists. It is compact but not maximally efficient.

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?

With an output schema available, the description need not explain return values, and it does mention cost and signing. However, the parameter schema descriptions are generic and the description does not compensate for ambiguous semantics around timeframe, source, or instrument, leaving some invocation uncertainty.

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 schema technically documents all six parameters. The description adds only the phrase 'explicit range,' implicitly tying to start/end, and gives no additional guidance on format, source, timeframe, or instrument. Baseline 3 is appropriate.

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?

The description states the resource and scope clearly: 'Signed bar series over an explicit range.' It also names the sibling it is not (`get_market_history_bulk`), so an agent can distinguish the two without opening either schema, though the phrasing of that distinction is awkward and repetitive.

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 tool rather than `get_market_history_bulk` for market history, giving an alternative and selection condition. It does not give broader when-not conditions, but the key routing decision is covered.

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.