Online Kommentar 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_commentariesC | Searches for legal commentaries based on a query and filters. |
| get_commentary_by_idC | Retrieves a specific commentary by its ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves a specific commentary by ID, while the other searches for commentaries based on queries and filters. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with snake_case naming: get_commentary_by_id and search_commentaries. The naming is predictable and readable throughout.
With only two tools, the server feels thin for a legal commentary domain. It lacks essential operations like creating, updating, or deleting commentaries, which limits its utility and scope.
The tool surface is severely incomplete for a legal commentary server. It only provides retrieval and search capabilities, missing core CRUD operations (create, update, delete) and other lifecycle management tools, leading to significant gaps in functionality.