Entscheidsuche MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_case_lawC | Search for Swiss court decisions using Entscheidsuche database |
| get_documentC | Retrieve the full content of a specific legal document |
| list_courtsB | Get information about available courts and their document counts |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| legal_research | Template for conducting legal research with case law search |
| case_analysis | Template for analyzing specific legal cases |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| court-status | Current status of all courts and scrapers |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_document retrieves specific document content, list_courts provides metadata about courts, and search_case_law performs searches across the database. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_document, list_courts, search_case_law) with clear, descriptive verbs. There are no deviations in naming conventions, making the set predictable and easy to understand.
With only 3 tools, the server feels somewhat thin for a legal document search domain. While the tools cover core operations (retrieve, list, search), more comprehensive coverage might include tools for filtering, advanced search, or document metadata management, suggesting a borderline appropriateness.
The tools provide basic CRUD-like operations (get, list, search) for legal documents and courts, but there are notable gaps. For example, there is no tool for updating or deleting documents, managing user queries, or handling advanced search parameters, which could limit agent effectiveness in complex workflows.