Skip to main content
Glama

Latest settled market regime (free)

sample_reading
Read-onlyIdempotent

What was the US market regime at the last close? Returns the newest settled Regime Card reading, the same one regimecard.com shows: a score from 0 to 100, one of five regimes, the eight cross-asset category labels, and the paid routes with their prices. Free. One reading per US trading day, settled at 4:30 PM ET. Useful as a free first look at the response shape and the paid routes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: one reading per US trading day, settled at 4:30 PM ET, and the exact composition of the response. It omits rate limits or free-tier restrictions, which keeps it from 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?

It leads with the question the tool answers, then the return contents, then cadence, then the preview use case — a sensible front-loaded order. Minor waste: 'Free' is repeated (in the title and as a standalone sentence) and the closing sentence restates the preview value already implied.

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 no output schema, the description carries the burden of describing return values, and it does so concretely (score range, regime enum size, eight category labels, paid routes with prices). Combined with the settlement timing, an agent has everything needed to call it and interpret the result.

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 takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool is 4. The description correctly signals that the call needs no input by framing it as a single fixed question.

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

Purpose4/5

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

The description opens with a concrete question it answers and states a specific verb+resource: it returns 'the newest settled Regime Card reading' with enumerated contents (0-100 score, five regimes, eight category labels, paid routes with prices). This clearly separates it from a live/intraday sibling, though it never names that sibling explicitly, so an agent must infer the settled-vs-live distinction.

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?

'Useful as a free first look at the response shape and the paid routes' implies a trial/preview use case, and the daily-settlement cadence implies when the data is stale. However, there is no explicit when-to-use vs when-to-use-something-else statement, and no named alternative such as the live reading for intraday needs.

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