prolog-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loadProgramA | Loads Prolog program definitions that can be queried later |
| runPrologQueryA | Executes a Trealla Prolog query against loaded definitions |
| saveSessionA | Saves the current Prolog session to a file for later loading |
| loadSessionB | Loads a previously saved Prolog session |
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 4 tools
The tools are mostly distinct: loadProgram and loadSession both involve loading, but the former loads program definitions while the latter restores a full session. runPrologQuery and saveSession are clearly separate, and descriptions help disambiguate the two load operations.
All tool names follow a consistent camelCase verb_noun pattern: loadProgram, runPrologQuery, saveSession, loadSession. The repeated 'load' verb is coherent for different loading operations.
Four tools is a well-scoped, compact set for a Prolog server, covering the essential actions without redundancy or bloat.
The core workflow is fully supported: load programs, run queries, and persist/restore sessions. Minor gaps like session reset or program listing are absent, but they are not critical for the primary use case.