Skip to main content
Glama

CatalystDesk

get_delayed_regime_lite

Get free 15-minute-delayed context.

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": "get_delayed_regime_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: data is 15-minute delayed (freshness limit) and free (no paid entitlement needed). It says nothing about auth requirements, rate limits, or what the returned "context" contains, so the disclosure is partial.

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?

It is a single short sentence with no padding, so it is concise, but the brevity comes at the cost of substance rather than from efficient expression of a complete idea.

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 tool with one undocumented required parameter, no output schema, and no annotations, the description should explain what "context" is returned and how it differs from get_regime_snapshot. Neither is present, leaving the agent to guess at output shape and selection criteria.

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 the single required `ticker` parameter, and the description adds no meaning — no format, no supported symbol universe, no reference to list_curated_symbols for discovering valid values. The schema's maxLength=12 is the only constraint available.

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

Purpose2/5

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

"Get free 15-minute-delayed context" names a verb but leaves the resource undefined — "context" could mean anything, and the name's "regime" hint is not carried into the description. It gives no basis for distinguishing this from sibling get_regime_snapshot, which plausibly returns similar data.

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 offers no when-to-use guidance, no exclusion conditions, and no reference to alternatives such as get_regime_snapshot or compute_dynamic_regime. "Free" and "delayed" weakly imply a cheap/preview tier, but the agent must infer that.

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