Skip to main content
Glama

Get a Swiss court decision

get_court_decision
Read-only

Retrieves a Swiss court decision by its ID from entscheidsuche.ch, returning metadata, a document link and a plain-text excerpt for review or citation.

Instructions

Fetch one court decision from entscheidsuche.ch by its id (from search_court_decisions, e.g. 'CH_BGer_005_5A-123-2020_2020-06-15'). Returns metadata (reference, date, court, canton, title, abstract), the document link and a plain-text excerpt of the decision (up to ~20 KB).

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_court_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDecision id from search_court_decisions
languageNoPreferred language for title/abstract
max_charsNoMaximum excerpt length in characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new behavioral context by naming the upstream data source, enumerating the returned metadata fields, and stating the ~20 KB excerpt cap so the agent can budget context. It omits failure behavior for an unknown or malformed id, which keeps it from a 5.

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?

Two sentences, front-loaded with the action and resource, followed by the return shape. No filler, no repetition of the title, and every clause carries information the agent needs.

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 present, the description carries the return-value burden and does so well by listing metadata fields, the document link, and the excerpt. The remaining gap is error/edge-case behavior for invalid ids, which is minor for a read-only single-record fetch.

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%, so the baseline is 3, and the description earns an increment by explaining where the id comes from and showing a concrete example format that the schema's regex alone does not convey. It also ties the 'up to ~20 KB' excerpt statement to the max_chars parameter, though it says nothing about the language parameter's effect.

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 uses a specific verb and resource ('Fetch one court decision from entscheidsuche.ch by its id') and immediately distinguishes this lookup-by-id tool from the sibling search tool that produces the id. The inline example id ('CH_BGer_005_5A-123-2020_2020-06-15') makes the expected identifier shape unambiguous.

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?

It clearly routes the agent through search_court_decisions as the source of the id, which is the main prerequisite for calling this tool. It stops short of stating when not to use it (e.g. that it cannot list or filter decisions), but there is no realistic competing sibling for a by-id fetch, so the guidance is adequate.

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