prolog-reasoner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROLOG_REASONER_LLM_MODEL | No | LLM model for library mode | gpt-5.4-mini |
| PROLOG_REASONER_LOG_LEVEL | No | Log level for the server | INFO |
| PROLOG_REASONER_SWIPL_PATH | No | Path to SWI-Prolog executable | swipl |
| PROLOG_REASONER_LLM_API_KEY | No | API key for library mode only — leave unset for MCP | |
| PROLOG_REASONER_LLM_PROVIDER | No | LLM provider for library mode (openai or anthropic) | openai |
| PROLOG_REASONER_LLM_TEMPERATURE | No | LLM temperature for library mode | 0.0 |
| PROLOG_REASONER_LLM_TIMEOUT_SECONDS | No | LLM timeout for library mode | 30.0 |
| PROLOG_REASONER_EXECUTION_TIMEOUT_SECONDS | No | Execution timeout for Prolog | 10.0 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_prologB | Execute Prolog code and return reasoning results. Write Prolog facts and rules, then run a query against them. Supports CLP(FD) constraints, negation-as-failure, and all standard SWI-Prolog features. |
| list_rule_basesA | List all saved rule bases with description and tags. Returns |
| get_rule_baseB | Retrieve the Prolog source of a saved rule base. |
| save_rule_baseA | Save a named rule base containing Prolog rules that can be reused
across Use this for stable, reusable knowledge (e.g. |
| delete_rule_baseC | Delete a saved rule base by name. |
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 5 tools
Each tool targets a distinct action: delete, execute, get, list, or save rule bases, with no overlap in functionality.
All tool names follow a clear verb_noun pattern with snake_case (e.g., delete_rule_base, execute_prolog), maintaining uniformity.
Five tools is well-scoped for a Prolog reasoning server, covering rule base CRUD and execution without excess or deficiency.
Core operations are present (CRUD for rule bases plus execution), but missing an explicit update tool; users must delete and re-save to modify a rule base.