Synthex Forge — x402 Paid Agent Services

Get Market History Bulk

get_market_history_bulk

Read-onlyIdempotent

Signed bulk bar series, up to 20 pairs. use it rather than get_market_history for market history bulk, not market history; an object with 35 fields including allowlist, batch_manifest. $5 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.
`pairs`	No	The pairs 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

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.
`index`	No	The `index` 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.
`reason`	No	Why the verdict was reached.
`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.
`results`	No	The results the operation produced.
`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.
`total_rows`	No	The `total_rows` field of the response.
`generated_at`	No	The `generated_at` field of the response.
`sha256_scope`	No	The `sha256_scope` field of the response.
`batch_manifest`	No	The `batch_manifest` field of the response.
`requested_bars`	No	The `requested_bars` field of the response.
`requested_days`	No	The `requested_days` field of the response.
`requested_pairs`	No	The `requested_pairs` field of the response.
`partial_failures`	No	The `partial_failures` 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.

Changed37 schema fields changedOct 31, 2026

addedOutput schema / properties / allowlist

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

addedOutput schema / properties / batch_manifest

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

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

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

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

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

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

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

addedOutput schema / properties / results

Added value: +{
+  "description": "The results the operation produced.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

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

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

Added value: +{
+  "description": "The `total_rows` 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.5/5.0

Behavior4/5

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

Beyond annotations, it discloses that results are signed, capped at 20 pairs, and cost $5 USDC, which is operationally important context for a paid read. It also notes an object of 35 fields including allowlist and batch_manifest, though this is partially redundant given the output schema.

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?

It is short, but the structure is poor: semicolon-separated fragments, a confusing aside about market history versus bulk market history, and a price note tacked on the end. Every element earns its place, yet the ordering is not front-loaded cleanly.

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?

The output schema and annotations cover return shape and safety, and the description adds pricing, signing and batch size. It still omits the meaning of start/end, resolution of the bars, and what signing verifies, which matters for correct invocation.

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. The description adds only the 20-pair limit tied to the pairs parameter and nothing about start/end semantics, bar interval or format meaning, so it does not meaningfully improve parameter understanding.

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 identifies the resource specifically: signed bulk bar series with a ceiling of 20 pairs, and explicitly contrasts it with get_market_history. The phrasing is awkward and the verb is missing, but an agent can tell what the tool returns and that it is a bulk variant.

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

Usage Guidelines3/5

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

It does name the alternative and says to use this rather than get_market_history for bulk history. However, the sentence 'for market history bulk, not market history' is garbled and self-referential enough that the boundary condition is only implied, not cleanly stated.

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.