Skip to main content
Glama

Get index series

get_index
Read-onlyIdempotent

A named daily index series (e.g. eu-vps-floor-2c4g, h100-list-median, frontier-input-floor) with its latest value, the number of constituents and the constituents themselves, so the value can be recomputed. Omit series to list all series with their latest values.

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_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, 1 to 3650
seriesNoSeries slug; omit to list all series

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 establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavioral context: the series is daily, results include the constituent breakdown enabling recomputation, and omitting the slug flips the tool into a list-all mode. Permissions and rate limits are not mentioned, but are lower priority for a read-only lookup.

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?

Two sentences, no filler, and the listing mode is stated last so the primary behavior leads. The first sentence is an overlong noun phrase with a nested clause about recomputation, which slightly slows comprehension compared to a verb-led opener.

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, it is essential that the description characterize the returned payload, and it does so explicitly (latest value, constituent count, constituents). The days look-back parameter is left entirely to the schema, which fully documents it, so nothing critical is missing for a two-parameter read tool.

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?

Schema coverage is 100%, so baseline would be 3, but the description contributes concrete example slugs (eu-vps-floor-2c4g, h100-list-median, frontier-input-floor) that show the agent the naming convention to construct a valid value. The omit-to-list behavior is repeated from the schema rather than added, and the days window is not discussed in the description at all.

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 specific resource (a named daily index series) and enumerates what comes back: latest value, constituent count, and the constituents themselves so the value can be recomputed. It is clear what the tool delivers, though the opening is a noun phrase rather than a verb and it never distinguishes itself from siblings like get_price.

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?

The only usage guidance is the mode switch: 'Omit series to list all series with their latest values,' which tells the agent how to trigger the list behavior. There is no when-to-use versus an alternative tool, no mention of when the index view is preferable to get_price or get_history, and no stated exclusions.

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