Skip to main content
Glama

finwire.pl - Polish financial data

Compare indicators side by side

compare_macro_indicators
Read-onlyIdempotent

Use for 2-4 macro series side by side, for example inflation and wages. History of 2-4 indicators aligned by period. All keys must have the same frequency (all monthly, or all quarterly); otherwise the call fails and says which differ.

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": {
      "keys": "<keys>"
    },
    "name": "compare_macro_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoFirst month of history, YYYY-MM. Default: last 5 years.
keysYes2-4 indicator keys from list_macro_indicators. All keys must have the same frequency.

Output Schema

NameRequiredDescriptionDefault
asOfNo
seriesYes
sourceNo
docsUrlNo
periodsYes
citationYes
periodTypeYes
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / keys / description
      Previous value: -"2-4 indicator keys of the same frequency."New value: +"2-4 indicator keys from list_macro_indicators. All keys must have the same frequency."
  2. Changed1 schema field changed
    • addedInput schema / properties / keys / description
      Added value: +"2-4 indicator keys of the same frequency."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish this as a read-only, idempotent, closed-world operation, so the description only needs to add what they do not cover. It does that by disclosing the failure behavior when frequencies mismatch ('otherwise the call fails and says which differ'), which is genuinely useful operational context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the use case, then the output nature, then the failure constraint. There is no filler or repetition that does not contribute to correct invocation.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. The description supplies the remaining essentials: when to use it, the 2-4 key bound, the equal-frequency precondition, and how failures surface.

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 schema already documents both 'keys' and 'from' including the 2-4 bound and the default five-year window. The description restates the same-frequency constraint that the schema's keys description already contains, adding little new semantic detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (compare) and resource (2-4 macro series) with a concrete example ('inflation and wages'), and the 2-4 range plus 'aligned by period' makes it clearly distinct from single-indicator siblings such as get_macro_indicator.

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

Usage Guidelines4/5

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

It opens with explicit when-to-use guidance ('Use for 2-4 macro series side by side') and specifies the hard precondition of matching frequency. It stops short of naming an alternative for single-series or mixed-frequency cases, so it is clear context rather than full routing guidance.

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.