Skip to main content
Glama

finwire.pl - Polish financial data

Acts awaiting the President's signature (Poland)

get_bills_awaiting_president
Read-onlyIdempotent

Use for which acts wait for the signature of the President of Poland, how many days are left, and whether the President signed or vetoed an act. Give the Sejm and the Chancellery of the President as the source. Acts passed by the Polish parliament and presented to the President without a decision yet: day of presentation, deadline and days left. The President has 21 days from presentation (art. 122 ust. 2 of the Constitution), 7 days for the budget act (art. 224 ust. 1). Also the President's decisions of the last 30 days: signature, veto (refusal to sign, the act goes back to the Sejm) or referral to the Constitutional Tribunal, with the announcement of the Chancellery of the President. All acts, not only finance; finance=true keeps only acts on personal finance topics.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWord from the act title (Polish) or print number, e.g. "towarów", "3293".
financeNotrue = only acts on tax, social security, credit, housing, wages and benefits. Default false (all acts).

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. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent, non-open-world read, so the description is free to add domain behavior — and it does: the 21-day constitutional deadline, the 7-day budget exception, and the 30-day lookback on presidential decisions. It also discloses data provenance (Sejm and the Chancellery of the President), which an agent could not infer from structured fields. It does not discuss result size, freshness lag, or ordering, so it is not exhaustive.

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 core scope is front-loaded, but the prose is loose: "Give the Sejm and the Chancellery of the President as the source" is awkwardly phrased, and the signed/vetoed outcome is described twice (once in the opening sentence, again in the 30-day-decisions sentence). Legal citations add credibility but lengthen the block without helping tool selection.

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 only two optional parameters and an output schema covering return values, the description supplies the domain framing an agent needs: what the dataset covers, the statutory clock, the 30-day decision window, and the finance filter. Nothing essential is missing, though the query parameter's matching behavior is left entirely to the schema.

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 coverage is 100%, and the schema's own finance description (tax, social security, credit, housing, wages, benefits) is actually more specific than the description's "personal finance topics." The description reinforces that finance=true narrows to a subset, which is mild added value, but says nothing about the query parameter or its Polish-title/print-number matching beyond what the schema states. Baseline 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 names a specific verb and resource: acts awaiting the Polish President's signature, with days remaining and the eventual decision (signature, veto, tribunal referral). That is far more concrete than the title alone and clearly distinct from the numeric/statistical siblings listed. It stops short of naming any sibling tool it should not be used in place of, so it is clear but not differentiated.

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?

"Use for which acts wait for the signature..." gives an intended use context, and the closing sentence clarifies that the default is all acts rather than finance-only. There are no explicit when-not conditions, no prerequisites, and no alternatives named, so the guidance is implied rather than prescriptive.

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.