Skip to main content
Glama
Sign In
bus-scheduling-mcp

bus-scheduling-mcp

by uwmyuan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scheduling_get_route_details

Retrieve complete route details, including stations and departure times, by providing a route ID. Use this to access specific scheduling information for any bus route.

Instructions

Get details of a specific route including stations and departures by route ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "route_id": "<route_id>"
    },
    "name": "scheduling_get_route_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
route_idYesThe ID of the route

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses what is returned (route details, stations, departures), which is useful for a read operation. However, it does not state side effects, permissions, or response format, leaving some ambiguity for a tool with no annotation support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that conveys essential information with no filler. Every word contributes to understanding the tool's purpose and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and no output schema. The description covers the core purpose and what to expect (stations and departures). It could mention that the route ID must be valid, but overall it is sufficiently complete for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with a description for route_id ('The ID of the route'). The description does not add much beyond this, merely restating 'by route ID'. Since the schema already covers the parameter, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' with a clear resource 'route details' and clarifies the scope via 'including stations and departures' and 'by route ID'. This clearly distinguishes it from the sibling tool scheduling_list_routes, which lists routes rather than details of a specific one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by route ID' implies the tool is used when you already have a route ID and need detailed information, while list_routes would be used to discover routes. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools