Skip to main content
Glama
U.S. Market Regime Traffic Light MCP

U.S. Market Regime Traffic Light MCP

explain_regime_model

Read-only

Explains what GREEN, YELLOW, and RED market-regime signals mean, what each metric measures, how often it updates, and the model's limitations.

Instructions

Explain what GREEN / YELLOW / RED mean, what each metric measures, update cadence and the model's limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explain_regime_model"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The `readOnlyHint: true` annotation already establishes that the tool is a safe read operation, so the description does not need to restate that. It does provide useful behavioral information beyond the annotations by listing the exact contents of the explanation: the meaning of each regime state, what each metric measures, update cadence, and the model's limits. The update cadence is especially useful, because it tells the consumer how current the underlying data is. The description does not describe the response format, but that is a minor gap for an explanatory tool.

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

Conciseness5/5

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

The description is a single sentence that front-loads the core purpose ('explain what GREEN / YELLOW / RED mean') and then lists the secondary topics. Every clause carries information, and there is no filler or repetition.

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

Completeness5/5

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

With zero parameters and no output schema, the description has to explain what the return value contains. It meets that obligation by enumerating the four topics the explanation covers. Nothing an agent needs in order to confidently select and call this tool is missing.

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

Parameters4/5

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

The tool accepts no parameters, so no parameter meaning is required. The description also indicates that the output is static documentation: it covers every regime state, so no filtering or scoping is suggested. This is the expected baseline of 4 for a tool with zero parameters.

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?

Names a specific verb+object pair — explains the meaning of values, what each measures, cadence, and limitations. This is complete enough to be called at the end of a conversation, and is not merely a restatement of the title, so it is also distinguishable from `get_market_regime`, which returns data rather than explaining how to interpret it.

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

Usage Guidelines3/5

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

The string does not state when to call this tool versus `get_market_regime`. However, the word 'explain' and the list of covered topics strongly imply its purpose, so an agent would probably infer that this is documentation rather than data retrieval. Still, no explicit routing rule or prerequisite is written.

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

Deploy Server

Other Tools