Skip to main content
Glama

AINDEX

The 11 S&P sectors

sector_moves
Read-only

The SPDR sector funds (technology, financials, health care and the rest) with their moves over a day, 5 days, a month, the year to date and a year.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the exact performance horizons returned (1d, 5d, 1mo, YTD, 1y) and that the universe is the SPDR sector ETFs, which tells the agent what kind of output to expect. It does not mention data freshness or market-session dependence, keeping it short of 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 that identifies the resource first and the returned metrics second, with no filler. The parenthetical '(technology, financials, health care and the rest)' is slightly loose but efficiently conveys the coverage without listing all eleven.

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 parameters, no output schema, and only read-only annotations, the description carries the return-value burden and does so by enumerating the five time horizons and the fund universe. An agent knows enough to call it and interpret the result. Only the units/format of the moves (percent vs. absolute) is left unstated.

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 the baseline is 4 and there is nothing for the description to disambiguate. No parameter-level meaning is missing because no parameters exist.

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 a specific resource (SPDR sector funds covering technology, financials, health care, etc.) and states exactly what data comes back: moves over one day, five days, a month, YTD, and a year. That is far more concrete than the bare name 'sector_moves'. It doesn't differentiate itself from any sibling (get_stock_quotes, get_asset), but no sibling obviously overlaps in scope, so the gap is minor.

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?

Usage is only implied: an agent can infer this is the tool for broad sector-level performance rather than single-stock quotes. There is no explicit when-to-use statement, no exclusions, and no named alternative such as get_stock_quotes for individual tickers.

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