Skip to main content
Glama

crashtestyourstrategy

Describe one regime — self-portrait

describe_regime
Read-onlyIdempotent

USE WHEN you want to understand what one named synthetic regime is, and its nearest historical episodes. Single-regime introspection: median behavioural descriptors, z-scores vs the catalogue (what makes THIS regime distinct), an English characterisation, the 2 nearest neighbours, the nearest real historical episodes and a stylized-facts audit against real history. find_similar_regime ranks neighbours of a target; this says what one regime IS.

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": {
      "profile_hint": "<profile_hint>"
    },
    "name": "describe_regime"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_hintYesSynthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Valid values are listed by get_started (profile_hints) and the regimes://available resource.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / profile_hint / description
      Previous value: -"Synthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Discover valid values via the regimes://available resource."New value: +"Synthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Valid values are listed by get_started (profile_hints) and the regimes://available resource."
  2. Changed1 schema field changed
    • addedInput schema / properties / profile_hint / description
      Added value: +"Synthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Discover valid values via the regimes://available resource."
  3. First observed

TDQS

A4.3/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, closed-world, non-destructive), so the description's added value is the report contents: what dimensions are compared (z-scores vs the catalogue), how many neighbours are returned (2), and that a stylized-facts audit against real history is included. It stops short of cost, latency, or error behaviour, but for a pure introspection call this is solid disclosure beyond the annotations.

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?

The trigger is front-loaded in a 'USE WHEN' clause, followed by a compact inventory of return contents and a one-line sibling disambiguation. The output list is dense but each item is informative; only minor tightening would be possible.

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 an output schema, annotations, and a fully documented parameter already present, the description still supplies the scoping rationale and the sibling contrast an agent needs to route correctly. It omits nothing critical for invocation; a note on failure modes for an invalid identifier would make it fully rounded.

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?

There is one required parameter with 100% schema description coverage, and the schema already explains that valid values come from get_started (profile_hints) and the regimes://available resource. The description never mentions profile_hint or the identifier source, so it adds no meaning beyond the schema; baseline 3 is warranted.

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 verb+resource ('understand what one named synthetic regime is' / single-regime introspection) and enumerates the concrete outputs (median descriptors, z-scores, characterisation, 2 nearest neighbours, historical episodes, stylized-facts audit). It explicitly contrasts itself with find_similar_regime ('this says what one regime IS'), so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Opens with an explicit 'USE WHEN' trigger tied to the single-regime understanding task, and names the alternative tool plus the condition that selects it ('find_similar_regime ranks neighbours of a target; this says what one regime IS'). Both the when and the when-otherwise are stated directly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.