get_indicesMajor indices with recent history — use days_back (1..365, default 30) to see how markets have moved over a period.
| Name | Required | Description | Default |
|---|---|---|---|
| days_back | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnly, idempotent, and non-destructive behavior, so the bar for additional disclosure is lower. The description adds meaningful context about the time-window behavior and the type of information returned, which goes beyond the structured annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single well-structured sentence with no filler. The core purpose is front-loaded and the parameter usage follows naturally.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple, optional-parameter read-only tool with an output schema and comprehensive annotations. The description covers what the tool returns and how the parameter affects results, leaving no significant gap for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry the parameter meaning. It does so by providing the valid range (1..365), the default (30), and the effect on the result (market movement over the period). It does not clarify the odd string typing of the parameter, but it provides substantial semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb and resource ('Major indices') and adds the distinguishing element of recent history over a configurable period. It does not explicitly call out how it differs from sibling tools like get_market_snapshot, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains the intended use of the days_back parameter and what the data shows, giving implied usage context. However, it does not state when to choose this tool over alternatives or mention any exclusions or complementary tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools map clearly to distinct resources: get_* for retrieval, list_* for enumeration, search_* for lookup, track_* for time series. Some overlap exists between get_executive_brief, get_executive_note, and get_executive_desk, and between get_indices and get_market_snapshot, but descriptions clarify the intended use. Overall an agent can usually tell which tool to pick with little ambiguity.
Tool names follow a highly consistent snake_case verb_noun pattern: get_, list_, search_, and track_ prefixes clearly indicate the operation. Resource nouns like executive_brief, risk_radar, world_events, and macro_series are descriptive and predictable. There are no mixed conventions or vague verbs.
Fifteen tools is on the higher end but remains within a reasonable range for a server covering briefs, notes, coverage areas, macro data, market snapshots, and risk tracking. Each tool has a plausible purpose, though a few could arguably be consolidated, such as the separate executive brief/note/desk retrieval tools. The count does not feel bloated or excessive for the stated scope.
The tool surface covers the core lifecycle of the domain: listing and retrieving briefs, coverage, macro series, indices, risk radars, and world events, plus search for macro indicators. Minor gaps exist, such as no way to search editorial briefs or coverage notes by keyword, and no direct retrieveal of catalysts beyond a forward horizon. These are workable gaps and do not prevent most agent workflows.