Skip to main content
Glama

finwire.pl - Polish financial data

Law changes radar

get_legal_changes
Read-onlyIdempotent

Use for new laws and for the next PIT, ZUS and VAT deadlines. For the full yearly calendar of a business, use get_compliance_calendar. Acts of the Journal of Laws and Monitor Polski on personal finance, tax, labour and housing: entering into force soon and recently, with plain-language summaries, plus bills in the Sejm. Also returns the next 30 days of the finwire legal calendar (series finwire_legal_calendar): PIT, ZUS and VAT deadlines, IKE/IKZE year end, value changes, RPP meetings and bond sales.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window for recent acts, default 30.
limitNoActs per list, default 8.
topicNoTopic key or word, e.g. "pit", "zus", "kredyty", "mieszkania", "placa_minimalna".

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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioural context beyond that: plain-language summaries accompany the acts, bills in the Sejm are included, and the finwire_legal_calendar series contributes a fixed next-30-days window (IKE/IKZE year end, RPP meetings, bond sales). It does not say whether the calendar slice is affected by the days parameter, which is the only remaining ambiguity.

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?

Front-loaded with the primary use case, then the alternative, then the content inventory. The final sentence is a long comma-separated enumeration that could be trimmed, but every clause carries actual information about returned content.

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 covering safety, full schema coverage, and an output schema that handles return shape, the description needs only to scope content and routing, which it does. The one gap is whether the embedded 30-day calendar responds to the days parameter, which an agent might reasonably wonder about.

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%, so days, limit and topic are already documented, including the topic examples. The description adds only marginal meaning, hinting that the 30-day calendar window is fixed while days is a look-back window for acts, but it does not state that relationship clearly enough to count as added semantics.

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?

States the concrete resources it returns: acts from the Journal of Laws and Monitor Polski on personal finance, tax, labour and housing (entering into force and recently in force, with plain-language summaries), bills in the Sejm, and the finwire legal calendar. It also names the sibling it is not (get_compliance_calendar), so an agent can distinguish it without opening a schema.

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?

Explicit use case ('new laws and the next PIT, ZUS and VAT deadlines') plus an explicit exclusion routing to get_compliance_calendar for the full yearly business calendar. That is a when-to-use and a when-to-use-something-else in one breath.

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.