finwire.pl - Polish financial data

finwire index registry

list_finwire_indices

Read-onlyIdempotent

All indices computed by finwire.pl, each under a stable id finwire_* (e.g. finwire_mortgage_barometer, finwire_credit_capacity_index, finwire_deposit_rate_index, finwire_savings_rate_index, finwire_rcn_price_index, finwire_price_gap_index, finwire_entry_threshold_index, finwire_credit_market_index, finwire_nowcast, finwire_legal_calendar): latest reading with its period, change vs the previous reading, method version and citation. Use get_finwire_index for one index with history.

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

Input Schema

Name	Required	Description	Default
`group`	No	Group: kredyt (credit), oszczednosci (savings), mieszkania (housing), rynek (market and forecasts), prawo (law).
`status`	No	live (default) = with a reading; planned = id reserved, in preparation.

Output Schema

Name	Required	Description	Default
`url`	Yes
`asOf`	No
`data`	No
`title`	Yes
`source`	Yes
`docsUrl`	Yes
`license`	Yes
`summary`	Yes
`citation`	Yes
`datasetId`	Yes
`sourceUrl`	No
`truncated`	No
`serverDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing what each entry contains (reading, period, delta, method version, citation), something annotations and schema do not convey.

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?

The core purpose and the sibling redirect are front-loaded, and the trailing sentence about get_finwire_index is well placed. The ten enumerated id examples are informative but make the first sentence long; a few examples would have sufficed.

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 annotations, a 100% documented schema, and an output schema handling return shape, the definition covers what an agent needs to select and call it. Only minor gaps remain, such as not characterizing registry size or ordering of results.

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% and both parameters are fully enum-documented with parenthetical glosses for the group values. The description adds no filter semantics of its own beyond the id examples, 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 names a specific verb and resource: it enumerates all finwire indices, gives the stable id convention with concrete examples, and lists the fields each entry carries (latest reading, period, change, method version, citation). It also explicitly separates itself from get_finwire_index, which returns one index with history.

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 clearly routes single-index/history lookups to get_finwire_index, leaving this tool implied for scanning the whole registry. It does not say when to use the group/status filters versus listing everything, but the alternative routing is explicit and unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All finwire.pl - Polish financial data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.