Skip to main content
Glama
Sign In

crashtestyourstrategy

by io.github.fnobbe
OverviewDiscussionsAdmin

Get raw regime series (synthetic replica or historical episode)

get_regime_data
Read-onlyIdempotent

USE WHEN you want the raw price series behind a synthetic regime or a historical episode, to recompute a claim yourself. source='historical' + ref=<case_id> returns a real-market anchor episode (dates, closes; OHLCV with include_ohlcv) and the descriptors computed on it; source='synthetic' + ref=<profile_hint> [+ seed] returns one cached replica (closes, warmup_index) and its descriptors. An empty ref lists the available ids and sample seeds. Recompute the descriptors from the closes to verify any claim the platform made. Same data as the regime-data:// resources, for clients that cannot read resources.

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": {
      "source": "<source>"
    },
    "name": "get_regime_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNohistorical: a case_id such as 'spy_lehman_2008'; synthetic: a profile_hint such as 'whipsaw_synthetic_spy'. Empty lists the available ids.
seedNosynthetic only: the replica seed (default: the lowest in the bundle; listed in the response as available_seeds).
sourceYes'historical' (a real-market anchor episode) or 'synthetic' (one cached replica).
include_ohlcvNoAlso return open/high/low/volume (about 5x larger); close alone is enough to recompute the descriptors.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds real context beyond them: caching of replicas, the empty-ref listing behavior, the ~5x payload cost of include_ohlcv, and the default-seed rule. It stops short of describing return payload details, which the output schema covers.

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?

Front-loaded with 'USE WHEN' and organized by source mode, which is the right structure. The sentences are dense but nearly every clause carries information; only the closing resource-parity note is slightly redundant with the routing already stated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and the description covers both modes, the listing behavior, defaults, and the alternative access path. An agent has everything needed to call it correctly.

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 each parameter already carries a description covering seed defaults, empty-ref listing, and OHLCV size. The description restates the source/ref pairing but adds no syntax or format detail the schema lacks, so baseline 3 is correct.

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?

The description names a specific verb and resource ('raw price series behind a synthetic regime or a historical episode') and draws the line between the two source modes. It also distinguishes itself from descriptor-oriented siblings by emphasizing raw series 'to recompute a claim yourself.'

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?

The 'USE WHEN' opener gives clear context, and it explicitly routes resource-incapable clients here instead of the regime-data:// resources. It does not explicitly contrast with sibling tools like describe_regime, so the when-not guidance is implied rather than stated.

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

All crashtestyourstrategy toolsInspect
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