Skip to main content
Glama
Sign In
mcp-saos

mcp-saos

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_by_case

Read-onlyIdempotent

Search Polish court rulings by case number (sygnatura akt). Retrieves decisions from Supreme Court, Constitutional Tribunal, common courts, and KIO.

Instructions

Skrot: szuka orzeczenia po sygnaturze akt (np. 'I ACa 772/13', 'IV CSK 123/15', 'KIO/UZP 100/12'). Odpowiednik search z parametrem caseNumber. Jesli sygnatura nie znajdzie sie w SAOS, sprawa moze byc z sadu administracyjnego (WSA/NSA - nieindeksowane) lub jeszcze nieopublikowana w bazie. Bledy: missing_arg (brak caseNumber), upstream_error.

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": {
      "caseNumber": "<caseNumber>"
    },
    "name": "search_by_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseNumberYesSygnatura akt, np. 'I ACa 772/13'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and open-world. The description adds valuable context about potential missing results and reasons, and lists specific errors, enhancing transparency beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise paragraph covering purpose, examples, usage equivalence, failure scenarios, and errors, with no superfluous content.

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?

For a simple tool with one required parameter and no output schema, the description addresses purpose, parameter, error handling, and limitations, making it sufficiently complete.

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 schema itself defines the parameter. The tool description provides examples and explains the format, adding modest value but not essential new meaning.

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?

The description clearly states it searches for judgments by case number, provides examples, and distinguishes it from the sibling 'search' tool by noting it is an equivalent shortcut with a specific parameter.

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?

The description explains that it is equivalent to 'search' with caseNumber, and clarifies scenarios when results may be missing (administrative court or not yet published). It gives error types but lacks explicit when-not-to-use or alternative tool guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools