Schema | bus-scheduling-mcp

bus-scheduling-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`API_BASE_URL`	No	Base URL of the Bus Scheduling Backend API, including /api path.	http://localhost:8000/api

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
scheduling_get_kpiA	Fetch key performance indicators (KPIs) like vehicle status, total departures, punctuality rate.
scheduling_get_trendsB	Get passenger flow trends for recent dates.
scheduling_list_routesA	List all active bus routes with optional filtering by dataset or company.
scheduling_get_route_detailsA	Get details of a specific route including stations and departures by route ID.
scheduling_list_plansA	List all algorithmically generated scheduling plans.
scheduling_get_gantt_dataB	Get plan tasks formatted as Gantt chart data by dataset or plan ID.
scheduling_get_optimization_algorithmsA	List available scheduling optimization algorithms (e.g., circular timetable, shift sequence).
scheduling_run_optimizationB	Trigger an optimization task with a specific algo_id and parameters. Returns a task ID.
scheduling_get_optimization_statusA	Get the status (running, completed, failed) of a specific optimization task by its task ID.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/uwmyuan/transit-scheduling-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server