search_everythingSearch stops, routes, and bus station destinations with a single query. Returns categorized results for each type.
Search stops, routes, and bus station destinations with one query.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum items per category. | |
| query | Yes | Search query. |
Changes observed during successful MCP inspections.
v0.2.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It only states what is searched and that one query spans multiple types, but it does not disclose how results are combined, what matching semantics apply, whether results are paginated, or what the response structure looks like.
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 a single, tightly scoped sentence that front-loads the main action and resource scope. There is no repetition of the title or unnecessary filler, and every word contributes to understanding 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?
For a simple search tool with fully documented input parameters, the description conveys the core function adequately. However, with no output schema and no annotations, it leaves the result format and behavior of the combined search unspecified, which an agent may need in order to correctly interpret the response.
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?
The input schema already documents both parameters with 100% coverage ('Search query.' and 'Maximum items per category.'). The description adds the conceptual framing that one query spans multiple categories, which is useful, but it does not add parameter-level detail beyond the schema, so the baseline of 3 applies.
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 names a specific verb ('Search') and the exact resources ('stops, routes, and bus station destinations') while emphasizing the combined nature of the query. This clearly distinguishes it from the narrower sibling tools like search_stops, search_routes, and search_bus_station_destinations.
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 description implies this tool is for searching across multiple resource types at once, but it does not explicitly state when to prefer it over the specific sibling search tools. No exclusions or alternative routing are provided, leaving the usage context to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.