Skip to main content
Glama

BestBus: Thailand bus times & tickets

Destinations from a town

buses_from
Read-only

Where intercity buses go from a Thai town, busiest routes first, with departures a day and the lowest fare. From BestBus's nightly data.

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": {
      "town": "<town>"
    },
    "name": "buses_from"
  }
}

Input Schema

NameRequiredDescriptionDefault
townYesTown in English, e.g. Krabi
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only/non-destructive safety, and the description adds real value beyond them: result ordering ('busiest routes first'), the fields returned ('departures a day and the lowest fare'), and data provenance/freshness ('BestBus's nightly data'). It does not state behavior for an unknown town or how the nightly snapshot affects coverage, keeping it short of a 5.

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?

Two compact sentences with no waste; the core purpose and ordering are front-loaded before the data-source note. Nothing could be cut without losing 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?

With only two parameters, no output schema, and annotations carrying the safety profile, the description covers what the tool returns and how it is sorted, which is what an agent needs to select it. Minor gaps remain around empty/no-route results and result-count behavior.

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 50%: 'town' is documented with a format hint ('Town in English, e.g. Krabi'), and the description reinforces that the input must be a Thai town. The 'limit' parameter is never mentioned in the description and relies entirely on its default/max constraints to be interpretable, so the description adds only partial value.

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

Purpose4/5

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

States a specific verb and resource: intercity bus destinations from a Thai town, returned busiest-first. The reverse-lookup direction ('from a town') implicitly distinguishes it from route_info and search_buses, but the siblings are never named, so the agent must infer the boundary itself.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of route_info or search_buses. The only signal is the implied 'I want to explore where I can go from X' framing, leaving the agent to guess between three bus-related tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources