Skip to main content
Glama

CatalystDesk

compute_execution_guardrail

Compute descriptive trade-liquidity and volatility guardrails.

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>"
    },
    "name": "compute_execution_guardrail"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
min_dollar_volNo
window_secondsNo
include_overnightNo
max_volatility_bpsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. "Compute" and "descriptive" weakly imply a side-effect-free read, but there is no statement about whether results are cached, whether thresholds are enforced/rejected, or what happens with defaulted optional parameters.

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

Conciseness3/5

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

A single front-loaded sentence with no wasted words, which is structurally clean. But the brevity reflects under-specification rather than economy — the one sentence omits everything an agent needs beyond the schema.

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 5-parameter analytical tool with no annotations, no output schema, and zero parameter documentation, the definition is far too thin. Key unknowns — whether optional thresholds default to null or a value, and what the return payload contains — are left entirely unresolved.

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% for 5 parameters, so the description must compensate and largely fails. It hints that min_dollar_vol relates to liquidity and max_volatility_bps to volatility, but says nothing about ticker format, meaning or default of window_seconds, or the effect of include_overnight.

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 names a specific verb ("compute") and a resource domain ("trade-liquidity and volatility guardrails"), so an agent can distinguish it from regime/resonance siblings. However, "guardrails" is unexplained jargon — it's unclear whether the tool returns threshold values, pass/fail checks, or raw metrics, so the actual output purpose stays fuzzy.

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 guidance on when to call this instead of siblings like compute_dynamic_regime or scan_curated_universe_regimes, and no stated prerequisites. The agent must infer usage purely from the word "guardrails."

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