Skip to main content
Glama

CatalystDesk

compute_dynamic_regime

Compute descriptive statistics over caller-defined non-time bars.

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>",
      "bar_type": "<bar_type>",
      "bar_threshold": "<bar_threshold>",
      "fast_period": "<fast_period>",
      "slow_period": "<slow_period>"
    },
    "name": "compute_dynamic_regime"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueNo
anchorNo
tickerYes
bar_typeYes
max_barsNo
fast_periodYes
slow_periodYes
bar_thresholdYes
process_var_qNo
anchor_epoch_sNo
include_overnightNo
measurement_var_rNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about determinism, cost, required inputs, or output shape. With twelve parameters and no indication of what is returned or how fast_period/slow_period alter behavior, an agent has no basis for predicting the call's effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but not efficient: it is under-specified rather than concise. Nothing is front-loaded beyond the barest verb phrase, and the misleading "non-time bars" clause wastes the only descriptive content the definition has.

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

Completeness1/5

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

For a twelve-parameter, five-required computation with no annotations and no output schema, the definition is radically incomplete. Neither the required-parameter contract nor the returned statistics are hinted at, leaving the agent unable to call the tool correctly from the description alone.

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

Parameters1/5

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

Schema description coverage is 0% across twelve parameters, and the description compensates for none of them. Terms like bar_threshold, process_var_q, and measurement_var_r (exponents of the variance ratio test) are entirely opaque, while fast_period/slow_period ranges of 2-199 and 3-200 go unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("Compute") and a resource ("descriptive statistics"), plus a scope hint ("caller-defined non-time bars"). But it never says which statistics, and "non-time bars" actively conflicts with the bar_type enum, which permits TIME_BAR. It does nothing to separate this tool from siblings such as compute_multiframe_resonance or scan_parameter_surface.

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?

There is no when-to-use guidance, no when-not to use, and no named alternative among the seven siblings. An agent cannot tell from this text whether this is the entry point for a regime workflow or a low-level primitive called after snapshot tools.

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