Skip to main content
Glama
Sign In

World Monitor

by app.worldmonitor
OverviewDiscussionsAdmin

Inflation, rates and yield history

get_macro_history
Read-onlyIdempotent

CPI, interest-rate and sovereign yield histories from seeded official-source reports. Select a dataset; country is required for world CPI or government yields. Default 30 newest observations per series, kept in chronological order; maximum 365. Set history=false for latest snapshots. Dates are Unix milliseconds, rates and yields are percentages. Missing readings or tenors are unknown, not zero. Series differ in source, frequency, index base and yield measure; a series records those that apply to its dataset. A truncated response is not full history; unavailable is not a zero reading.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset": "<dataset>"
    },
    "name": "get_macro_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum newest observations per series, in chronological order.
countryNoRequired for world-cpi and government-yields. Omit for US-only datasets. Pass an ISO 3166-1 alpha-2 code (e.g. "IQ"), an alpha-3 code ("IRQ"), or a country name in any supported dashboard locale (e.g. English "Iraq", Arabic "العراق", German "Deutschland", Chinese "中国").
datasetYesChoose US CPI, US interest rates, US Treasury par yields, country CPI, or sovereign yields.
historyNoTrue returns bounded history; false requests the latest available snapshot.
jmespathNoOptional JMESPath projection applied to the response. See initialize.instructions for grammar and examples.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"Required for world-cpi and government-yields. Omit for US-only datasets. Pass an ISO 3166-1 alpha-2 code (e.g. \"IQ\"), an alpha-3 code (\"IRQ\"), or an English country name (\"Iraq\")."New value: +"Required for world-cpi and government-yields. Omit for US-only datasets. Pass an ISO 3166-1 alpha-2 code (e.g. \"IQ\"), an alpha-3 code (\"IRQ\"), or a country name in any supported dashboard locale (e.g. English \"Iraq\", Arabic \"العراق\", German \"Deutschland\", Chinese \"中国\")."
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations by disclosing defaults and caps (30 newest, max 365, chronological order), units (Unix milliseconds, percentages), and the semantics of absence ('Missing readings or tenors are unknown, not zero', 'A truncated response is not full history'). It also warns that series differ in source, frequency, index base and yield measure, which prevents false cross-series comparison.

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?

Front-loaded with purpose then defaults then caveats, and nearly every clause carries operational information. The final two sentences overlap somewhat ('missing... unknown, not zero' vs 'unavailable is not a zero reading'), which is mild redundancy rather than waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, five-parameter, output-schema-backed data tool, the description covers what an agent needs to call it correctly: dataset choice, conditional country, limit bounds, ordering, units and the interpretation of gaps. Return shape is handled by the output schema, so nothing material is missing.

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 the baseline is 3, but the description adds real meaning on top: it explains what a dataset choice implies, that country is conditionally required, and that history=false yields a snapshot rather than a series. It still repeats limit/max values already in the schema and does not mention jmespath 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?

States a specific verb and resource set ('CPI, interest-rate and sovereign yield histories') and the source ('seeded official-source reports'), which is enough to distinguish it from a generic economic-data tool. It does not, however, name or differentiate from plausible siblings such as get_consumer_prices, get_economic_data or get_country_macro, so the agent must infer the boundary.

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?

Gives concrete selection rules inside the tool: 'Select a dataset; country is required for world CPI or government yields' and 'Set history=false for latest snapshots.' That is good intra-tool routing, but there is no guidance on when to use this tool instead of the overlapping sibling tools, and no stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All World Monitor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources