Skip to main content
Glama

Official rate and macro series in one call, by name

macro
Read-only

Official rate and macro series in one call, by name: fed_funds, us_cpi, us_core_cpi, us_unemployment, us_10y, us_2y, us_mortgage_30y, us_gdp, wti_oil, brent_oil, henry_hub_gas, us_house_price_index, ecb_deposit_rate, ecb_main_refi_rate and euro_area_hicp. Latest value, change vs previous and vs a year earlier, and observations. Up to 6 series. FRED (US public domain), the ECB Data Portal and Eurostat. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "series": "<series>"
    },
    "name": "macro"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoOnly observations from this date (YYYY-MM-DD) on
limitNoObservations per series, 1-120, default 12
seriesYesUp to 6 series names, comma-separated: fed_funds, us_cpi, us_core_cpi, us_unemployment, us_10y, us_2y, us_mortgage_30y, us_gdp, wti_oil, brent_oil, henry_hub_gas, us_house_price_index, ecb_deposit_rate, ecb_main_refi_rate, euro_area_hicp

Output Schema

NameRequiredDescriptionDefault
seriesNo
sourceNo
licenseNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "license": {},
      +    "series": {},
      +    "source": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.7/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 safety is covered. The description adds genuinely useful behavior beyond that: upstream data provenance (FRED, ECB Data Portal, Eurostat, with FRED noted as public domain) and a payment prerequisite ($0.002 per successful call via x402 USDC on Base/Solana plus 10 networks, with failed calls uncharged) — the latter is exactly the kind of auth/cost context an agent needs before invoking. It does not state whether results are cached or how a bad series name is reported, keeping it just 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?

Content is front-loaded: what you get in one call, then the valid names, then the returned measures, then source and price. The long series enumeration is duplicated near-verbatim from the schema, which is somewhat wasteful. Otherwise there is little padding.

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 an output schema present, the description need not detail return values, and it still briefly names them (latest value, change vs previous and vs a year earlier, observations). Sources, pricing and the six-series cap round out the operational picture. What is missing is error behavior for invalid series names and any note on update frequency of the underlying series.

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%, with descriptions for 'from', 'limit' (1-120, default 12) and the 'series' list already documented in the schema. The description only restates the series enumeration and the six-series cap, adding no semantics not present in the schema. Baseline 3 applies since the schema carries the explanatory burden.

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 definition exhaustively enumerates the resource (fed_funds, us_cpi, ecb_deposit_rate, wti_oil, etc.) and states what is returned for each series, so an agent knows exactly what domain this tool covers. It never names a competing sibling, but the sibling list here is largely unrelated, so differentiation is low-stakes. The only weakness is the absence of an explicit retrieval verb — the action is only implied by 'in one call, by name'.

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 constraints are conveyed indirectly: 'Up to 6 series' and 'by name' imply the comma-separated call pattern, and the schema repeats the same constraint. There is no statement of when this tool is preferred over a general data source or when it should not be used, and no mention of failure modes such as an unknown series name. Practical but with clear gaps.

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