Skip to main content
Glama

CatalystDesk

get_regime_snapshot

Get a live regime summary using caller-defined periods.

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": {
      "ticker": "<ticker>",
      "fast_period": "<fast_period>",
      "slow_period": "<slow_period>"
    },
    "name": "get_regime_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
fast_periodYes
slow_periodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure but only says the result is 'live' and period-driven. It omits what a 'regime summary' contains, whether the computation is expensive or rate-limited, what authentication may be required, and how 'live' differs from delayed data in practice.

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 definition is a single front-loaded sentence with no filler or repetition. It is efficiently structured, though its brevity is under-specification rather than genuine clarity, which is captured in other dimensions.

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

Completeness2/5

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

For a three-parameter required tool with zero schema description coverage, no annotations, and no output schema, the description is far too thin. It does not explain what the snapshot returns, how fast and slow periods interact, or what ticker formats are accepted, leaving an agent unable to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three required parameters. The description mentions 'periods' plural, vaguely mapping to fast_period and slow_period, but explains neither their distinct roles nor the meaning of 'ticker', and adds no format or constraint details beyond 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 states a specific verb+resource ('Get a live regime summary') and signals a live/delayed distinction that partially differentiates it from the 'get_delayed_regime_lite' sibling. However, it never explicitly distinguishes itself from other regime-related siblings like 'compute_dynamic_regime', leaving some ambiguity about scope.

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

Usage Guidelines2/5

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

The description provides no when-to-use guidance, no conditions for choosing this tool over the delayed or compute-based alternatives, and no prerequisites. 'Using caller-defined periods' is a hint about configuration but not actionable routing guidance.

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.

Resources