Skip to main content
Glama

SN Data by Shikshan Nivesh

US economic series

get_macro_series
Read-onlyIdempotent

US Treasury yields, the federal funds rate, CPI, core CPI, payrolls, unemployment, GDP and PCE. Each period has its latest value and, where held, the value first printed, so you can see what was known at the time and how it was revised. Leave out series to list them.

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

Input Schema

NameRequiredDescriptionDefault
toNoOnly periods on or before this date (year-month-day).
fromNoOnly periods on or after this date (year-month-day).
seriesNoLike cpi, nonfarm-payrolls, real-gdp, treasury-yields, fed-funds-target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds non-obvious behavior the annotations cannot: each period carries the latest value plus the value first printed, enabling point-in-time and revision analysis. It stops short of mentioning pagination, size limits, or default span when from/to are omitted.

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?

Three sentences, each earning its place: the series inventory, the vintage-value semantics, and the omit-series behavior. The opening sentence is a bare noun list with no verb, which makes the lead slightly less front-loaded than it could be, but there is no filler.

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 return-shape burden and does so reasonably by explaining that each period holds latest and first-printed values. All three parameters are schema-documented, so remaining gaps (default date range, units, pagination) are modest for a read-only, non-destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does add one piece of meaning beyond the schema by explaining that omitting series lists the available series, and the vintage-value sentence clarifies what 'period' values contain. It adds no syntax or format detail for from/to beyond what the schema already provides.

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 resource domain explicitly by enumerating the series covered (Treasury yields, fed funds, CPI, core CPI, payrolls, unemployment, GDP, PCE), which cleanly separates it from the company/fund siblings. It never states a verb such as 'retrieve' or 'return', so the purpose is inferred from the noun list rather than declared.

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?

'Leave out series to list them' gives one concrete usage behavior (discovery of available series), which is genuinely useful. There is no guidance on when to choose this over get_dataset or get_financials, and no stated exclusions or prerequisites, so the routing guidance is only implied.

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