Skip to main content
Glama

Pelnora: Polish law and court rulings

Orzeczenie

get_ruling
Read-only

Dokument po identyfikatorze (np. sn:…, saos:…, cbosa:…): metadane, documentKind (ruling = orzeczenie; legal_question, request, unknown to nie orzeczenia), tekst gdy polityka publikacji pozwala (inaczej textStatus i textNote; textNote przy tekście = uszkodzony fragment u źródła), powołane przepisy, citation. Wycofane: błąd 410.

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": {
      "id": "<id>"
    },
    "name": "get_ruling"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesidentyfikator orzeczenia z list (pole id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the minimal annotations (readOnlyHint, openWorldHint=false), the description discloses genuinely useful behavior: full text is returned only when publication policy allows, otherwise textStatus/textNote explain the omission, and a textNote accompanying text flags a corrupted fragment at the source. The withdrawn-document case is pinned to a concrete HTTP-style code (410), giving the agent a predictable failure mode.

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?

Content is front-loaded ('Dokument po identyfikatorze') and every clause carries information, but the single sentence is dense with nested parentheses and semicolons, making it harder to scan than a short bulleted list would be. No filler, though.

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 no output schema, the description does the work of enumerating return content: metadata, documentKind, text or textStatus/textNote, cited provisions and citation. Combined with the 410 error case and id format examples, an agent has what it needs to call and interpret the tool; only other failure modes (e.g. not-found handling) are unspecified.

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 there is only one parameter, so the baseline is 3, but the description adds value the schema lacks by enumerating the identifier namespaces (sn:, saos:, cbosa:). That helps the agent construct a valid id rather than just knowing it is a 3–200 character string.

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 concrete action and resource: fetch a document by identifier, illustrated with real identifier shapes (sn:, saos:, cbosa:). It also warns that documentKind may be legal_question, request or unknown, i.e. not actually a ruling, which sharpens what the tool returns. It does not explicitly contrast itself with siblings such as get_act or rulings_for_provision, so it stops short of a 5.

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?

Usage is implied rather than stated: the identifier is the 'id' field coming from list results, and the prefix examples show valid invocation input. The 410 case tells the agent what happens for withdrawn documents, but there is no explicit when-to-use-this-vs-alternatives guidance (e.g. when to use rulings_for_provision or search_docket instead).

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