Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

global_central_bank_macro_rates_inflation_tracker

Read-onlyIdempotent

Global Central Bank Macro Rates & Inflation API: Tracks policy interest rates, CPI inflation releases, and central bank decisions worldwide.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum macro indicators to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum macro indicators to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the 'worldwide' scope and the indicator categories. It says nothing about data freshness, update cadence, or whether results are current snapshots versus historical series, which matters for a 'tracker'.

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?

One sentence, front-loaded with the capability and indicator types, with no filler. It is efficient, though it reads largely as an expanded title and carries little operational detail.

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

Completeness3/5

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

For a one-optional-parameter read tool with rich annotations and no output schema, the definition is minimally sufficient. The main gap is return shape: whether the agent gets a time series per country or a single latest reading, which materially changes how it should be used.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains maxResults and its default of 10. The description adds no further meaning about how results are ordered or truncated when maxResults is hit, so the baseline 3 applies.

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?

Names a specific verb and resource set: tracks policy interest rates, CPI inflation releases, and central bank decisions, with a global scope. An agent can tell what data domain it serves. It stops short of differentiating from any concrete alternative, but the verb+resource pairing is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated exclusions, and no routing to an alternative for related needs (FX rates, macro-adjacent compliance data). Usage is only implied by the topic itself, leaving the agent to guess whether this fits a given macro question.

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