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

bus-scheduling-mcp

by uwmyuan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scheduling_list_routes

List active bus routes with optional filters for company or dataset to retrieve scheduling information.

Instructions

List all active bus routes with optional filtering by dataset or company.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scheduling_list_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of records to skip for pagination (default: 0)
limitNoMaximum number of records to return (default: 100)
companyNoFilter by company name
dataset_idNoFilter by dataset ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the 'active' filter behavior and optional filtering, but does not explicitly state read-only nature (though 'List' implies non-mutating) or response format. Pagination behavior is left to the schema.

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 with the verb 'List' and the resource. It is concise, efficient, and contains no unnecessary information.

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?

For a simple list tool, the description covers the core purpose and filtering options. However, it lacks usage guidelines and does not describe the response structure, which would be helpful given no output schema. The schema covers parameter details, so it remains reasonably complete.

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?

Schema coverage is 100%, with each parameter (skip, limit, company, dataset_id) described. The description adds that filtering by dataset or company is optional, which is consistent with the schema but does not introduce new semantics beyond what is already documented.

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 'List' and resource 'active bus routes', clearly stating the scope and optional filters by dataset or company. This distinguishes it from sibling tools like scheduling_get_route_details (for details) and scheduling_list_plans (for plans).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention that scheduling_get_route_details should be used for individual route details or that this is for overviews. There are no exclusions or prerequisites.

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