Euclid-MCP
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 |
|---|---|
| reasonC | Perform logical deduction on a knowledge base and return solutions with proof trees for each result |
| explainA | Explain, in natural language, how a query is proven: walk the proof tree of each solution and return readable reasoning steps. Rule IDs are cited when present. |
| diagnoseC | Diagnose why a query succeeds or fails. Modes: 'why' (explain success), 'why_not' (explain failure), 'what_needs' (what would make it succeed) |
| what_ifC | What-if analysis: apply modifications to a knowledge base and see how they affect query results. Use + prefix to add facts, - prefix to remove facts. |
| check_kbC | Check a knowledge base for consistency: syntax errors, undefined predicates, circular rules, duplicates. |
| register_kbA | Register a named knowledge base under a kb_id so later calls can reference it instead of resending the KB text. Overwrites an existing kb_id. The KB is validated with check_kb first. |
| unregister_kbA | Remove a named knowledge base from the registry. Returns 'removed': false when the kb_id is not registered. |
| list_kbsA | List the registered named knowledge bases (metadata only: kb_id, content_hash, version, counts). |
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 8 tools
Several tools overlap in purpose: reason, explain, and diagnose all deal with explaining or producing query outcomes, making it hard to know which to call. diagnose even includes a 'why' mode that duplicates explain. The KB management tools are clear, but the reasoning tools blur together.
Naming is mixed: some tools use bare verbs (reason, explain, diagnose), some use snake_case verb_noun (register_kb, unregister_kb, list_kbs, check_kb), and what_if deviates entirely from the pattern. The style is inconsistent across the tool set.
Eight tools is a well-scoped size for a knowledge-base reasoning server. Each tool contributes to either KB lifecycle management or query/reasoning workflows without feeling padded or sparse.
The KB lifecycle is covered well: register, unregister, list, and check. Reasoning coverage includes query, explanation, diagnosis, and what-if analysis. Minor gap: there is no way to retrieve the actual content of a registered KB, only metadata, which agents may need for inspection.