Skip to main content
Glama

finwire.pl - Polish financial data

One macro indicator with history

get_macro_indicator
Read-onlyIdempotent

Use for the value, the meaning or the trend of one macro indicator. One indicator by key with its meaning, latest reading, freshness, next release and history (oldest first) with min and max over the window.

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": {
      "key": "<key>"
    },
    "name": "get_macro_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesIndicator key from list_macro_indicators, e.g. "cpi-rr".
fromNoFirst month of history, YYYY-MM. Default: last 5 years.

Output Schema

NameRequiredDescriptionDefault
asOfNo
sourceNo
docsUrlNo
historyYes
citationYes
indicatorYes
serverDateYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds substantive behavior: history is ordered oldest first, and min/max aggregates are computed over the requested window. It does not state limits on history length or behavior when the key is unknown, which keeps it from 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?

Two sentences, front-loaded with the use case before the payload contents; no filler or repetition of the title. The second sentence is dense but each clause (ordering, aggregates, release info) contributes distinct information.

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?

For a two-parameter read tool with full annotation coverage, a complete schema, and an output schema, the definition supplies plenty: what fields return and how history is ordered and aggregated. Return-format detail is mildly redundant with the output schema, but nothing an agent needs to invoke it correctly is missing.

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 both `key` (pattern plus an example 'cpi-rr') and `from` (YYYY-MM format plus a documented 5-year default) fully specified. The description adds only the loose notion of 'by key' and 'the window', which the schema already carries, 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?

The description names a specific verb+resource ('the value, the meaning or the trend of one macro indicator') and enumerates exactly what comes back: meaning, latest reading, freshness, next release, and history. The singular 'one indicator by key' implicitly separates it from multi-indicator siblings such as compare_macro_indicators, but no sibling is named explicitly.

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?

'Use for the value, the meaning or the trend of one macro indicator' gives a clear use context, and the schema notes the key must come from list_macro_indicators, which implies a discovery step. However, no alternatives are named and there is no when-not guidance — an agent cannot tell from the description alone whether to pick this over get_macro_snapshot or get_macro_changes for a related 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.