Skip to main content
Glama

AINDEX

The whole market now, and how its parts relate

market_today
Read-only

The S&P 500, Nasdaq 100, Dow, VIX, the US 10-year, the dollar, gold, oil, BTC and ETH with the day's move; the 11 sectors over a day to a year; gainers, losers and most active; market headlines; this week's earnings for stocks with a Robinhood token; the economic calendar; the US session. links: breadth across the verified Robinhood stocks (up, down, cap-weighted and median move), the best and worst sector and the spread, which way the indexes, VIX, yields, the dollar, gold, oil and bitcoin point today, Nasdaq against the S&P, bitcoin against the Nasdaq, earnings this week and high-impact releases ahead. Measured relations, not a view.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds real behavioral context the annotations don't: it discloses that the 'links' section is derived cross-asset analysis ('bitcoin against the Nasdaq') over 'verified Robinhood stocks', which tells the agent results are computed, not opinionated. It does not say anything about quote freshness, snapshot timing, or how the day boundary is defined, which matters for a 'today' tool.

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

Conciseness2/5

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

The text is a single semicolon-chained paragraph that reads as an inventory dump rather than a structured definition; there are no headings separating the raw snapshot from the derived 'links'. Content is also duplicated — sector coverage appears twice ('the 11 sectors over a day to a year' and again 'the best and worst sector and the spread'). Dense, but hard to scan and longer than the information requires.

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 full burden of describing return values, and it does so thoroughly across every section the tool produces. An agent knows what data comes back. What is missing is operational framing — freshness, and how this bundle differs from the sibling market tools — rather than content coverage.

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 zero parameters, so there is no parameter meaning to explain and no schema gap to compensate for. Baseline 4 applies; nothing in the description confuses the empty input contract.

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 names the exact resource set it returns — 'The S&P 500, Nasdaq 100, Dow, VIX, the US 10-year, the dollar, gold, oil, BTC and ETH with the day's move' plus sectors, movers, headlines, earnings and the calendar. That is a concrete, specific scope an agent can recognize. It stops short of a 5 because it never distinguishes itself from the many market siblings (market_overview, market_brief, market_dossier, get_market_session), so the agent cannot tell which market view to pick.

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 when-to-use statement at all — no thresholds, no prerequisites, no named alternative. The only implicit signal is the closing line 'Measured relations, not a view,' which hints this is descriptive rather than opinionated, but the agent must infer that contrast. With four similarly named market tools available, the absence of routing guidance is a real cost.

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