Skip to main content
Glama

Nalegalu MCP

by io.github.nalegaluorg
OverviewDiscussionsAdmin

search_case_by_signature

Read-only

Verify a cited case signature (sygnatura), e.g. "II CSK 448/14".

    Use before relying on a judgment cited by a user or another agent.
    Answers from a local index of all SAOS judgments first; only on a
    local miss does it query live SAOS. Read the verdict field:
    "confirmed" (matches listed with saos_id, court, date, type —
    different courts reuse signatures, so check the court), "not_found"
    (strong evidence the citation is fabricated or wrong),
    "outside_coverage" (administrative courts NSA/WSA are not in SAOS —
    verify in CBOSA instead), "unverified" (local miss and SAOS
    unreachable; do not treat as nonexistent). Optional court_type:
    COMMON, SUPREME, CONSTITUTIONAL_TRIBUNAL, NATIONAL_APPEAL_CHAMBER.
    has_text=false on a match means SAOS stores no text for it, so
    verify_quote cannot check quotes against that judgment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
signatureYes
court_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses the local-index-first-then-live-SAXS lookup order, the exact verdict semantics (confirmed/not_found/outside_coverage/unverified) with interpretation guidance, the warning that courts reuse signatures, and the has_text implication for verify_quote.

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-loads the core purpose and the example, and every block of text carries actionable content. It is dense and slightly list-like, but no sentence is filler.

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?

An output schema exists, yet the description still pre-empts the most decision-critical return field (verdict), which is exactly what an agent needs to interpret results and route to alternatives like CBOSA or verify_quote.

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 0%, so the description must compensate; it supplies an example signature format and enumerates the court_type values (COMMON, SUPREME, CONSTITUTIONAL_TRIBUNAL, NATIONAL_APPEAL_CHAMBER) that the schema only types as a bare string. The 'limit' parameter remains unexplained, so it is not fully compensating.

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?

States a specific verb+resource ('Verify a cited case signature') with a concrete example, and its verification role is clearly distinct from siblings like get_case, research_cases, and verify_quote.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ('before relying on a judgment cited by a user or another agent') and gives a when-not/alternative route ('administrative courts NSA/WSA are not in SAOS — verify in CBOSA instead').

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

All Nalegalu MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources