clickbus_search_placesSearch bus terminals and cities by name to identify departure or arrival points before planning trips. Returns place matches only; no bookings are made.
Read-only place search (terminals/cities). Does not book a ticket.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| privacy_mode | No | ||
| response_format | No | markdown |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, and the description reinforces this with 'Read-only' and 'Does not book a ticket.' This adds clear user-facing context about expected side effects beyond the raw annotation flags.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler. It front-loads the read-only nature and the place-search scope, making it easy for an agent to quickly understand the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The core behavior is captured and the safety profile is well covered by annotations. However, the description omits guidance on how privacy_mode affects results and does not explicitly route the agent to clickbus_search_trips for trip-related searches, leaving moderate room for misinterpretation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description provides no explanation of the parameters. 'query' is somewhat self-evident, and the enums for response_format are clear, but 'privacy_mode' with values summary/structured/raw is ambiguous without additional explanation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'search' and the resource 'places', adding the parenthetical '(terminals/cities)' to define scope. It does not explicitly differentiate from sibling clickbus_search_trips, but 'places' vs 'trips' provides reasonable distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Read-only place search' and 'Does not book a ticket' imply this is for lookup rather than booking or modification. However, it does not explicitly state when to prefer this over clickbus_search_trips or provide any exclusions beyond the no-booking note.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.