Quellgeist
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_logsA | Query structured incident logs; optional since/level/route; rows carry a stable int 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 1 tool
With only one tool, there is no possibility of confusing it with another tool. The purpose of query_logs is clearly defined and distinct.
The single tool name follows a clear verb_noun pattern (query + logs), which is consistent, descriptive, and follows common conventions.
A single tool feels too few for a server focused on incident logs, as typical workflows would likely require additional operations such as fetching a specific log entry or listing available log sources.
The server provides only a query operation, missing obvious capabilities like retrieving a single log by ID or managing log sources. While querying is the core operation, the lack of additional functions creates notable gaps for common use cases.