Skip to main content
Glama

finwire.pl - Polish financial data

What changed recently

get_macro_changes
Read-onlyIdempotent

Use when the user asks what is new in macro data. Indicators whose reading was updated in the last N days (newest first), with the change against the previous reading.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window, default 7.

Output Schema

NameRequiredDescriptionDefault
asOfNo
daysYes
countYes
sourceNo
changedYes
docsUrlNo
citationYes
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior, so the description only needs to add context beyond safety. It adds the result ordering and the comparison semantics (change vs. previous reading), which the annotations do not cover. What remains unstated, such as how many indicators can come back or how null previous readings are handled, is minor for a read tool.

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?

Two sentences, both earning their place: the trigger comes first, then the precise output semantics. There is no filler, hedging, or repetition of the title.

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 single optional-parameter read tool with full annotation coverage and an output schema, the description covers the trigger, filter, ordering, and payload shape. Nothing an agent needs in order to call 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 coverage is 100% and the days parameter already documents its 1-60 range and default of 7. The description's 'last N days' merely restates the window concept without adding format or edge-case detail, so the baseline 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 names the resource (macro indicators), the precise filter (reading updated in the last N days), the ordering (newest first), and the payload (change against the previous reading). That is enough to separate it from get_macro_indicator, get_macro_snapshot, and get_macro_calendar without inspecting their schemas.

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 gives an explicit trigger: 'Use when the user asks what is new in macro data.' That is a clear when-to-use condition, but it names no alternatives or exclusions, so an agent must infer that a user wanting a single indicator's value should go elsewhere.

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.