Skip to main content
Glama
Sign In
AIT-Complex-Dynamical-Systems

pypddlengine

by AIT-Complex-Dynamical-Systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pypddlengine

No user-submitted related servers found.

    Related Servers

    • AI-godot-mcp

      DC925928496
      A
      license
      C
      quality
      C
      maintenance
      Enables AI-driven game development by providing MCP tools to interact with the Godot editor, including scene editing, node manipulation, script attachment, and scene execution.
      28
      7 npm
      MIT
    • Planwright by soundheart-studios

      Planwrightofficial

      soundheart-studios
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents and humans to collaborate on local, evidence-driven planning by exposing MCP tools for plan listing and binding, workflow catalog/run operations, and task tracking with human-reviewed decisions.
      2
      AGPL 3.0

    • chess-mcp

      ShuiYi-bit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to play and analyze chess, validate moves, and view a live synchronized visual board in the browser through MCP tools.
      20 npm
      MIT

    • LLMMO Game Server

      MiloLug
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM-driven text game state management by exposing MCP tools for managing players, locations, items, entities, and abstract concepts.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    With 10 tools, the server is well-scoped. Each tool provides a necessary function for exploring PDDL problems without superfluous or missing functionality.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources