Synthex Forge — x402 Paid Agent Services

Get Market Calendar

get_market_calendar

Read-onlyIdempotent

Session hours, holidays and settlement cut-offs for a venue. use it rather than assess_market_regime for market calendar, not market regime; an object with 67 fields including abbreviation, algorithm. $0.01 USDC.

Input Schema

Name	Required	Description
`venue`	No	The venue this operation operates on. See the schema for its type and whether it is required.
`nowEpoch`	No	The nowEpoch this operation operates on. See the schema for its type and whether it is required.
`operation`	No	The operation to perform.
`tradeDate`	No	The tradeDate this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`id`	No	The `id` field of the response.
`ok`	Yes	Whether the operation succeeded.
`end`	No	The `end` field of the response.
`date`	No	The `date` field of the response.
`name`	No	The `name` field of the response.
`note`	No	A note on how the answer was produced.
`open`	No	The `open` field of the response.
`close`	No	The `close` field of the response.
`cycle`	No	The `cycle` field of the response.
`start`	No	The `start` field of the response.
`venue`	No	The `venue` field of the response.
`checks`	No	The individual checks that were run.
`detail`	Yes	Human-readable explanation of the verdict.
`nowUtc`	No	The `nowUtc` field of the response.
`offset`	No	The `offset` field of the response.
`reason`	No	Why the verdict was reached.
`result`	No	The `result` field of the response.
`sha256`	No	The `sha256` field of the response.
`status`	No	The status of the operation.
`isToday`	No	The `isToday` field of the response.
`openUtc`	No	The `openUtc` field of the response.
`verdict`	Yes	The decision this tool returned.
`closeUtc`	No	The `closeUtc` field of the response.
`critical`	No	The `critical` field of the response.
`findings`	No	The `findings` field of the response.
`nowEpoch`	No	The `nowEpoch` field of the response.
`segments`	No	The `segments` field of the response.
`severity`	No	The `severity` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`timezone`	No	The `timezone` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`assurance`	No	The `assurance` field of the response.
`localDate`	No	The `localDate` field of the response.
`localTime`	No	The `localTime` field of the response.
`operation`	No	The `operation` field of the response.
`timeBasis`	No	The `timeBasis` field of the response.
`tradeDate`	No	The `tradeDate` field of the response.
`utcOffset`	No	The `utcOffset` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`checksTotal`	No	The `checksTotal` field of the response.
`conventions`	No	The `conventions` field of the response.
`knownVenues`	No	The `knownVenues` field of the response.
`abbreviation`	No	The `abbreviation` field of the response.
`checks_total`	No	The `checks_total` field of the response.
`evaluated_at`	No	The `evaluated_at` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`isEarlyClose`	No	The `isEarlyClose` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`holidaySource`	No	The `holidaySource` field of the response.
`tablesVersion`	No	The `tablesVersion` field of the response.
`checksObserved`	No	The `checksObserved` field of the response.
`coverageWindow`	No	The `coverageWindow` field of the response.
`profileVersion`	No	Version of the answer profile.
`settlementDate`	No	The `settlementDate` field of the response.
`tables_version`	No	The `tables_version` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`checks_observed`	No	The `checks_observed` field of the response.
`durationMinutes`	No	The `durationMinutes` field of the response.
`knownOperations`	No	The `knownOperations` field of the response.
`profile_version`	No	Version of the answer profile.
`reproducibility`	No	The `reproducibility` field of the response.
`utcOffsetMinutes`	No	The `utcOffsetMinutes` field of the response.
`nowEpochIsSupplied`	No	The `nowEpochIsSupplied` field of the response.
`sessionTimesSource`	No	The `sessionTimesSource` field of the response.
`settlementCycleBasis`	No	The `settlementCycleBasis` field of the response.
`daylightSavingInEffect`	No	The `daylightSavingInEffect` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed68 schema fields changedOct 31, 2026

addedOutput schema / properties / abbreviation

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / assurance

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / checks

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / checksObserved

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

addedOutput schema / properties / checksTotal

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

addedOutput schema / properties / checks_observed

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

addedOutput schema / properties / checks_total

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

addedOutput schema / properties / close

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

addedOutput schema / properties / closeUtc

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

addedOutput schema / properties / conventions

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

addedOutput schema / properties / coverageWindow

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

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

addedOutput schema / properties / cycle

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

addedOutput schema / properties / date

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

addedOutput schema / properties / daylightSavingInEffect

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / durationMinutes

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

addedOutput schema / properties / ed25519Sig

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

addedOutput schema / properties / end

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

addedOutput schema / properties / evaluated_at

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

addedOutput schema / properties / evidenceCore

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

addedOutput schema / properties / findings

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

addedOutput schema / properties / holidaySource

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

addedOutput schema / properties / id

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

addedOutput schema / properties / isEarlyClose

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

addedOutput schema / properties / isToday

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

addedOutput schema / properties / knownOperations

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

addedOutput schema / properties / knownVenues

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

addedOutput schema / properties / localDate

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

addedOutput schema / properties / localTime

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

addedOutput schema / properties / name

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

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

addedOutput schema / properties / nowEpochIsSupplied

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

addedOutput schema / properties / nowUtc

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

addedOutput schema / properties / offset

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

addedOutput schema / properties / ok

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

addedOutput schema / properties / open

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

addedOutput schema / properties / openUtc

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

addedOutput schema / properties / operation

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

addedOutput schema / properties / profileVersion

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

addedOutput schema / properties / profile_version

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

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

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

addedOutput schema / properties / segments

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

addedOutput schema / properties / sessionTimesSource

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

addedOutput schema / properties / settlementCycleBasis

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

addedOutput schema / properties / settlementDate

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

addedOutput schema / properties / severity

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

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

addedOutput schema / properties / status / description
```
Added value: +"The status of the operation."
```

addedOutput schema / properties / tablesVersion

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

addedOutput schema / properties / tables_version

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

addedOutput schema / properties / timeBasis

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

addedOutput schema / properties / timezone

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

addedOutput schema / properties / tradeDate

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

addedOutput schema / properties / utcOffset

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

addedOutput schema / properties / utcOffsetMinutes

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

addedOutput schema / properties / venue

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

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), and the description adds genuinely new context: the call costs '$0.01 USDC' and returns an object of roughly 67 fields. Pricing is material behavior an agent cannot infer from annotations or schema. The field enumeration ('including abbreviation, algorithm') is garbled and only loosely useful.

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 purpose and the sibling routing are front-loaded, which is good, but the sentence is a run-on fragment stitched together with semicolons and a colon. The '67 fields including abbreviation, algorithm' clause is low-value and reads as machine-generated filler rather than information the agent can act on.

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 a full output schema and strong annotations, the description doesn't need to explain return values, and it doesn't. What's missing is operational context: valid venue identifiers, what `operation` selects, and expected formats for `tradeDate`/`nowEpoch`. For a 4-parameter tool with boilerplate schema text, that gap is noticeable but not crippling.

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 nominally 100%, so the baseline is 3. However, the schema text is pure boilerplate ('The nowEpoch this operation operates on. See the schema for its type...'), and the description adds meaning only for `venue`; it says nothing about `operation`, `tradeDate`, or `nowEpoch` formats. It neither compensates for nor worsens 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?

The description names the concrete resource and its contents: 'Session hours, holidays and settlement cut-offs for a venue', which is specific enough for an agent to know what it retrieves. It lacks an explicit verb (the 'get' is only implied by the name) and opens with a bare noun phrase, so it falls short of a clean verb+resource statement. It does differentiate itself from a sibling by name.

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 routes the agent away from a specific sibling: 'use it rather than `assess_market_regime` for market calendar, not market regime'. That is a real when-to-use rule with a named alternative. It stops short of stating exclusions or prerequisites (e.g., when a cached snapshot would suffice instead).

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.