Skip to main content
Glama

finwire.pl - Polish financial data

Legal limits and tax values

get_legal_limits
Read-onlyIdempotent

Use for statutory values of this year: IKE and IKZE limits, PIT and minimum wage. For next year, use get_next_year_limits (property tax: get_property_tax_next_year). Statutory values for the current year: IKE and IKZE contribution limits, PIT thresholds and rates, tax-free amount, capital gains tax, rental flat-rate tax, minimum wage and other limits; topic "local-tax" gives the upper limits of local property tax rates. Company tax regimes (CIT, Estonian CIT, IP Box) and business rules: get_business_guide.

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

Input Schema

NameRequiredDescriptionDefault
topicNoDefault limits.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 useful behavioral scope beyond that — what value domains are covered and that the 'local-tax' topic returns upper bounds of local property tax rates — but says nothing about freshness, units, or currency of the statutory values.

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 routing information is front-loaded and valuable, but the first and third sentences substantially restate the same list of current-year statutory values, making the description noticeably redundant. Tightening the two overlapping value enumerations into one would lose no information.

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 an output schema present and a single optional enum parameter, the description covers scope and routing adequately; return values need not be explained. The only mild gap is that it does not say which jurisdiction's statutory values these are or whether amounts are nominal at publication time.

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% and the only parameter's enum description is merely 'Default limits', which is thin. The description compensates by explaining what the alternate 'local-tax' branch returns (upper limits of local property tax rates), adding meaning the schema does not carry.

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 resource and enumerates its contents: IKE and IKZE limits, PIT thresholds and rates, tax-free amount, capital gains tax, rental flat-rate tax, minimum wage. It is clearly demarcated from get_next_year_limits and get_business_guide, so an agent can distinguish it from siblings without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing: use this for the current year, use get_next_year_limits for next year, get_property_tax_next_year for next-year property tax, and get_business_guide for CIT/Estonian CIT/IP Box and business rules. The when-to-use and when-to-use-something-else conditions are both stated.

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.