finwire.pl - Polish financial data

One finwire index with history

get_finwire_index

Read-onlyIdempotent

One finwire index by its id finwire_* (old dataset ids such as credit-market-index, borrowing-power or credit-stress are accepted as aliases): latest and previous reading with periods, change, method version, sources, citation formula and history. Indices computed from WIBOR publish only the result.

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": {
      "id": "<id>"
    },
    "name": "get_finwire_index"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	finwire_* id or alias, e.g. "finwire_entry_threshold_index".
`history`	No	History points, default 12.

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/5.0

Behavior4/5

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

The annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description need not restate safety. It adds meaningful behavioral detail: accepted legacy aliases and the caveat that WIBOR-computed indices publish only the result. It does not discuss auth, rate limits, or pagination beyond the schema's history cap.

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?

The definition is front-loaded with the core action and resource, then adds aliases and the WIBOR caveat in a compact two-sentence form. Every clause carries information; the parenthetical alias list is useful rather than redundant.

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?

Given the rich annotations, complete input schema, and existing output schema, the description supplies enough context to invoke the tool correctly: the id form, accepted aliases, returned reading/history content, and a WIBOR-specific caveat. It does not need to restate return fields already covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both id and history are already documented. The description still adds value by naming concrete legacy aliases such as credit-market-index, borrowing-power, and credit-stress, clarifying what 'alias' means in practice. It does not elaborate on the history parameter beyond what the schema already provides.

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?

It names a specific resource and action: one finwire index retrieved by id, with latest/previous readings, change, sources, citation formula, and history. The word 'One' distinguishes it from list_finwire_indices, but it does not explicitly route against other siblings such as get_dataset or compare_macro_indicators.

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?

Usage is implied: call this when you have a finwire_* id or accepted legacy alias and need one index. However, it never states when to use this versus list_finwire_indices to discover an id, or versus get_dataset/compare_macro_indicators for related tasks.

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.