Skip to main content
Glama
uwmyuan

bus-scheduling-mcp

by uwmyuan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to bus-scheduling-mcp

No user-submitted related servers found.

    Related Servers

    • Express REST API and MCP

      buir341
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to discover and invoke generated API actions as MCP tools and read context through MCP resources for list and get-by-id operations. It provides HTTP-based MCP access for clients such as Cursor and Claude without extra glue code.
      MIT

    • Express REST API and MCP

      rezende64
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to discover and invoke generated API operations as MCP tools and resources, supporting create, update, list, and get-by-id actions over the same data exposed by the REST API.
      MIT

    • agent-control

      loulanyue
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to orchestrate AI agents and tasks, inspect DAG workflows, monitor cluster metrics, and perform safe database queries and statements through standardized MCP tools.
      189
      Apache 2.0

    • semantic-runtime

      Chloride233
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to serve and query semantic models, providing tools for entity descriptions, metric lookups, context resolution, and operation validation for AI agents.
      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

    A3.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: routes, route details, Gantt data, optimization algorithms, running/status of optimizations, KPIs, trends, and plans. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent scheduling_<verb>_<noun> pattern using only snake_case. Verbs are limited to list, get, and run, making the naming predictable and coherent.

    Tool Count5/5

    9 tools is well within the ideal 3-15 range and each tool serves a clear purpose in the bus scheduling domain. The count is neither sparse nor overwhelming.

    Completeness4/5

    The tool set covers route viewing, optimization execution and status, KPIs, trends, and plan listing. However, there is no direct way to fetch the result of a specific optimization task (only status), nor a get_plan_details tool; the Gantt data requires a plan ID, which may not be known until after listing plans.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources