Skip to main content
Glama

Prawnet: Polish case law and legislation

Interpretacja podatkowa po sygnaturze

interpretacja
Read-onlyIdempotent

Metadane interpretacji KIS / EUREKA po sygnaturze: data, organ, kategoria, status, ocena stanowiska, teza (do 300 znaków), przepisy, słowa kluczowe, 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": {
      "sygnatura": "<sygnatura>"
    },
    "name": "interpretacja"
  }
}

Input Schema

NameRequiredDescriptionDefault
sygnaturaYesNp. "0114-KDIP4-2.4012.597.2024.2.MC"

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish the read-only, idempotent, closed-world, non-destructive profile. The description adds two useful behavioral facts: the response is metadata only ('Bez pełnej treści') and the thesis field is capped at 300 characters. It stops short of saying what happens on an unknown signature or which tool supplies the full text.

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?

A single compact sentence, front-loaded with the resource and key before the field list. The field enumeration is partly redundant with the output schema, but it usefully communicates the scope of what comes back.

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 a full output schema, complete parameter coverage, and rich annotations, the description only needs to set scope — which it does by flagging metadata-only results. The remaining gap is the absence of a pointer to the sibling that returns full interpretation text.

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% and the single parameter already ships a concrete example signature, so the schema carries the burden. The description only restates that lookup is by signature and adds no format, normalization, or validation guidance beyond the schema.

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 the resource (KIS/EUREKA tax interpretation metadata) and the lookup key ('po sygnaturze'), plus enumerates the returned metadata fields. This makes it distinguishable from a search-style sibling, but it never names such a sibling explicitly, so differentiation is left to inference.

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 is only implied by the phrase 'po sygnaturze' — an agent infers it applies when a signature is already known. There is no explicit when-to-use, when-not-to-use, or statement that a different tool handles keyword/theme search.

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