Skip to main content
Glama

U.S. Market Regime

get_us_market_regime

Read-onlyIdempotent

Fetch the live end-of-day U.S. market regime (GREEN/YELLOW/RED), risk score (0-100), QQQ vs 200d SMA & drawdown, VIX vs 20d average, SMH semiconductor relative strength, 25-day distribution count, and non-advisory educational risk-sizing context.

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

Input Schema

NameRequiredDescriptionDefault
include_methodologyNoInclude indicator methodology details in the response (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's extra value is in telling the agent the data is a live end-of-day snapshot rather than a historical query, that the risk score is bounded 0-100, and that output is explicitly educational/non-advisory. It stops short of describing response shape or update cadence, which holds it below a 5.

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?

A single front-loaded sentence with the verb and scope first, followed by the indicator list; each listed indicator corresponds to a real return field, so the enumeration earns its length. It reads as a run-on comma list rather than cleanly grouped content, which keeps it from a 5.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing returns and does so by naming every major field, satisfying the main gap. Remaining omissions — refresh cadence and response format — are minor for a zero-required-parameter read-only snapshot tool.

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

Parameters3/5

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

Schema description coverage is 100% and the single boolean parameter (include_methodology, default false) is fully documented in the schema itself. The description does not expand on what 'methodology details' include or when to set the flag, so it adds essentially nothing beyond structured data — the baseline 3.

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?

The description opens with a specific verb and resource ('Fetch the live end-of-day U.S. market regime') and then enumerates exactly what the payload contains: regime color, risk score, QQQ vs 200d SMA/drawdown, VIX vs 20d average, SMH relative strength, and distribution count. Nothing here overlaps with the sibling tools (a drawdown calculator and a chart drill), so an agent can identify this as the sole market-state snapshot tool.

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 statement of when to call this versus alternatives, no prerequisites, and no note on staleness or repeated invocation ('live end-of-day' hints at a snapshot but never says how fresh it is or whether it should be re-polled). The 'non-advisory educational risk-sizing context' phrase implies a use case (sizing decisions) but does not frame it as guidance for tool selection.

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.