zdte.ai SPX Market Structure

Regime Segment Tape

get_regime_segments

Read-onlyIdempotent

Only how the dealer regime changed during one past trading day, the compact replay: a list of regime segments with their start and end times; no walls, gamma flip, net GEX or spot. One replay date (YYYY-MM-DD) per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "get_regime_segments"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Replay date in YYYY-MM-DD, one of the dates in the replay date catalog.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / date / description

Previous value: -"Replay date in YYYY-MM-DD; use list_history_dates for the set of valid dates."New value: +"Replay date in YYYY-MM-DD, one of the dates in the replay date catalog."

First observedSep 5, 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 the description adds genuinely useful scope disclosure: the exclusions (no walls, gamma flip, net GEX, spot) tell the agent this is a narrow content window rather than a full snapshot. It does not mention pagination or response ordering, but the content-boundary disclosure is the valuable part.

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?

Dense and front-loaded: the scope is stated first, exclusions second, and the parameter constraint last. It is written as a verbless fragment, which is slightly awkward, but every clause carries information.

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?

With no output schema, the description steps in to say the return is a list of regime segments with start and end times, which is what an agent needs to consume the result. Nothing important is missing for a simple one-parameter read tool.

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 coverage is 100% and the schema already gives the pattern and the 'replay date catalog' constraint, so the baseline is 3. The description only restates the YYYY-MM-DD format and adds that it is one date per call, which is largely implied by the single-property schema.

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 resource (regime segments for one past trading day) and explicitly scopes it against richer siblings by ruling out walls, gamma flip, net GEX and spot. An agent can distinguish this from get_regime or get_market_structure without opening any 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?

Frames the call as the 'compact replay' for when only the regime change tape is wanted, and states the one-date-per-call constraint. It never names the alternative tool (e.g. get_regime) that would be used when the excluded fields are needed, so selection is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All zdte.ai SPX Market Structure 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.

Resources

Need Help?