Skip to main content
Glama
Praharsh-Projects

mobility-operations-agent-platform

Related Servers

Alternatives to mobility-operations-agent-platform

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server that exposes BiziDashboard's historical and analytical data for the Zaragoza Bizi bike-share system as tools for LLM clients, enabling queries on rankings, occupancy patterns, mobility signals, alert history, and station rebalancing diagnostics.
      9
      11 npm
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server exposing distributed industrial asset data (battery storage, EV chargers, solar arrays) with tools for asset status, geospatial search, alerts, anomaly explanation, and load simulation.
      781 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that exposes the UAM vertiport simulator as tools for AI-assisted analysis, enabling simulations, KPI analysis, and what-if studies via Claude Desktop.
      -
    • A
      license
      B
      quality
      B
      maintenance
      MCP server that provides F1 telemetry analysis, tyre degradation modeling, and pit strategy recommendations, delivering race engineer-style calls grounded in real data. It exposes tools for degradation fits, fuel correction, and strategy reasoning via LangGraph.
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server that exposes fleet telemetry queries as tools for language models, enabling natural language questions about vehicle positions, trips, and alerts. Runs on the operator's machine and returns aggregated results from a SQLite database.
      -

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct domain area: charging risk, mobility metrics, and policy retrieval. No overlap or ambiguity exists between their purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: 'query_' or 'retrieve_' followed by a specific noun. No mixing of conventions.

    Tool Count5/5

    Three tools is appropriate for a focused mobility operations domain. Each tool provides essential, non-redundant functionality without overwhelming the agent.

    Completeness4/5

    The tool set covers key informational needs (charging risk, metrics, policy) but lacks any action-oriented tools (e.g., update, create). This is acceptable for a query-focused agent, but operations may require more than just retrieval.

    Maintenance

    ActivityStale
    ResponsivenessNo issues