finwire.pl - Polish financial data

Tax on profit paid from Poland to another country

get_tax_treaty

Read-onlyIdempotent

Use for tax on dividends, interest or royalties paid abroad. Also use for the countries that invest the most in Poland (NBP data). Give the legal basis and the verification date of each fact. Polish withholding tax on dividends, interest and royalties paid to a resident of a country: the statutory rate, the rate in the double tax treaty with Poland (portfolio and qualified holding), whether MLI modifies the treaty, and the EU/EEA/Swiss parent-subsidiary exemption with its holding conditions. Covers the largest investor countries by NBP data; without country returns the list and the ranking.

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

Input Schema

Name	Required	Description	Default
`lang`	No	Language of texts, default en.
`country`	No	ISO2 code, e.g. DE, NL, US.

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 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive safety traits. The description adds scope-specific behavior: it covers NBP-based investor countries, and without a country it returns the list and ranking. The instruction to give a legal basis and verification date is somewhat ambiguous, but the description still adds useful context beyond the annotations.

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 opening is front-loaded and relevant, but the description repeats the investor-country idea in the first and last sentences and duplicates the 'paid abroad' framing. The dense colon list is informative but could be tightened.

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?

For a two-parameter read-only lookup with an output schema and full parameter descriptions, the description is largely complete: it explains the treaty-rate topic, the MLI/EU exemption scope, and the no-country fallback. Minor ambiguity around 'Give the legal basis' keeps it from being fully complete.

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 the baseline is 3. The description adds meaning beyond the schema by explaining what happens when country is absent and by framing country as a resident country for treaty-rate lookup.

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 that the tool is for tax on dividends, interest, or royalties paid abroad, and also for the list of countries investing most in Poland. This is a specific verb-and-resource purpose, but it does not explicitly distinguish itself from siblings such as get_tax_rulings.

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 clear usage cues with 'Use for...' and 'Also use for...', and explains the no-country fallback returns the list and ranking. It does not name exclusions or alternative tools, so it falls short of full when-not guidance.

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.