finwire.pl - Polish financial data

Investment funds in Poland (IZFiA)

get_investment_funds

Read-onlyIdempotent

Use for investment fund assets and net flows: equity, bond, mixed and PPK funds. Assets, purchases of units, redemptions and net flows of investment funds in Poland from monthly IZFiA data: whole market, fund groups (short-term bond, bond, equity, mixed, PPK, target date, absolute return, commodity, crypto assets, private market) with IZFiA profiles, bond funds by type, equity funds by region, net flows since January and over 12 months, and the finwire index finwire_fund_flows_index (12-month net flows as % of assets a year earlier). Amounts in PLN million. Informational data, not investment advice.

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_investment_funds"
  }
}

Input Schema

Name	Required	Description	Default
`history`	No	Number of past months in the summary, 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 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context: data is monthly, amounts are in PLN million, and it explicitly disclaims investment advice. It does not cover rate limits or authentication, but those are less relevant for a read-only data tool.

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

Conciseness3/5

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

The description is a single dense paragraph that lists many fund categories and data dimensions. While information-rich, it reads as a run-on and could be structured more clearly for quick scanning.

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?

The description covers the data source, frequency, units, scope, and disclaimer, and an output schema exists. It is nearly complete for an agent to call the tool correctly, though it does not state how far back the monthly data extends.

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?

The schema fully documents the single 'history' parameter (0–60 months, default 12). The description does not mention this parameter or add any meaning beyond the schema, so the baseline of 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 states a specific resource (investment fund assets and net flows in Poland from IZFiA) with detailed subcategories. It clearly identifies the tool's scope but does not explicitly differentiate it from siblings such as get_ike_ikze_stats or get_finwire_index.

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?

The opening phrase 'Use for investment fund assets and net flows' gives clear context on when the tool applies. However, it offers no when-not-to-use guidance or explicit alternatives, which keeps it short of a 5.

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.