Skip to main content
Glama

Prawnet: Polish case law and legislation

Szukaj interpretacji podatkowych

szukaj_interpretacji
Read-onlyIdempotent

Interpretacje indywidualne i wiążące informacje stawkowe/akcyzowe KIS z portalu EUREKA (2003–05.2026, 538 866 dokumentów): wyszukiwanie w tezie, słowach kluczowych i początku treści, filtr lat wydania i przepisu ustawy podatkowej. Zwraca do 10 najnowszych: sygnatura, data, organ, status, ocena stanowiska, teza (do 300 znaków), przepisy, link EUREKA. Bez pełnej treści.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fraza": "<fraza>"
    },
    "name": "szukaj_interpretacji"
  }
}

Input Schema

NameRequiredDescriptionDefault
frazaYesSłowa (bez odmiany); OR, "…", -słowo. Do 200 znaków
rok_doNo
rok_odNo
przepisNoNp. "art. 86 ustawy o VAT", "art. 22 updof"

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed world), and the description adds substantial behavior on top: the exact corpus and date coverage, that only the 10 newest matches come back, that teza is truncated to 300 characters, and that full document text is not returned. These limits materially affect how an agent should plan queries.

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 resource and corpus, then the search scope, then the return shape. Dense but every clause carries information; the only minor cost is that the opening sentence is packed with parenthetical facts that slow parsing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only search tool with a rich output schema, a documented corpus, explicit result limits, and truncation/omission caveats – an agent has everything needed to decide to call it and to interpret the response. The missing piece (full text retrieval) is correctly out of scope for this tool.

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 50% – fraza and przepis are documented in the schema while rok_od/rok_do are not, and the description compensates by explaining they are year-of-issuance filters. It also adds that fraza matches against thesis, keywords, and the beginning of the content, meaning beyond the schema's syntax note.

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?

Names a specific verb and resource ('wyszukiwanie' of 'Interpretacje indywidualne i wiążące informacje stawkowe/akcyzowe KIS'), plus the source portal, date span, and corpus size (538 866 dokumentów). An agent immediately knows this is a search tool over KIS interpretations, distinguishable from siblings like szukaj_orzeczen or interpretacja.

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?

States the searchable fields (teza, słowa kluczowe, początek treści), the filter options (lata wydania, przepis ustawy), and a hard result cap of 10 newest documents, which tells the agent the recall characteristics. It never explicitly names when to prefer a sibling (e.g., fetching full text via a document-retrieval tool), only implying it with 'Bez pełnej treści'.

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.

Resources