pypddlengine
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pddl_initA | Initialize a PDDL exploration session with a domain and problem. Must be called first before using other tools. |
| pddl_init_from_filesA | Initialize a PDDL exploration session by reading domain and problem from files. Use this instead of pddl_init when the PDDL definitions are available as files, to avoid duplicating large strings in the conversation. |
| pddl_get_available_actionsA | Get all actions that can be executed in the current state. Returns action names and arguments. |
| pddl_execute_actionB | Execute a PDDL action with given arguments. Returns success status, new state summary, and whether goal is reached. |
| pddl_get_current_stateA | Get the complete current state, including all true predicates and fluents. |
| pddl_is_goal_reachedB | Check if the goal state has been reached. |
| pddl_resetA | Reset to the initial state and clear action history. Use this to try a different approach. |
| pddl_get_action_historyA | Get the history of all actions taken so far in this session. |
| pddl_get_domainA | Get the PDDL domain string used to initialize this session. Useful for re-reading action schemas, predicates, and types. |
| pddl_get_problemA | Get the PDDL problem string used to initialize this session. Useful for re-reading objects, initial state, and goal conditions. |
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 10 tools
Each tool targets a distinct aspect of PDDL exploration: initialization, action querying, execution, state inspection, goal checking, history, and domain/problem retrieval. There is no overlap or ambiguity.
All tools follow a consistent 'pddl_<verb>_<object>' pattern (e.g., pddl_init, pddl_get_available_actions, pddl_execute_action). The naming is uniform and predictable.
With 10 tools, the server is well-scoped. Each tool provides a necessary function for exploring PDDL problems without superfluous or missing functionality.
The tool set covers the full lifecycle of a PDDL exploration session: initialization, action enumeration, execution, state queries, goal detection, reset, history, and retrieval of domain/problem definitions. No obvious gaps remain.