Search the Rooster Agent Gateway directory of verified, bookable real-world businesses. Filter by category, city, service area or minimum rating. Returns matching businesses with their id, category, location, rating, verification status and booking action.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| category | No | e.g. Dentist, MedicalBusiness, HVACBusiness, RealEstateAgent | |
| min_rating | No | ||
| service_area | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint is true and the description indicates a pure search/return operation with no side effects. No contradictions. It does not mention pagination or result limits, but the read-only annotation covers the main behavioral transparency concern.
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?
Two concise sentences that state the purpose, filter options, and return fields without redundancy or unnecessary detail.
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 description lists the return fields (id, category, location, rating, verification status, booking action), compensating for the absent output schema. It does not mention pagination or result limits, but for a directory search tool the provided context is largely sufficient.
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?
Only category has a schema description, but the main description names all four filters: category, city, service area, and minimum rating. Parameter names are mostly self-explanatory, though min_rating lacks bounds/format and service_area could be ambiguous with city.
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?
Clearly states it searches the Rooster Agent Gateway directory of verified, bookable businesses and returns matching businesses. Distinct from sibling tools book and get_business by focusing on discovery/search rather than retrieval or booking.
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?
Description explicitly lists supported filters (category, city, service area, minimum rating), making the search use case clear. It does not explicitly contrast with get_business or book, but the search-oriented wording strongly implies when it should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct function: searching for businesses, getting a single business's full profile, and performing a booking handoff. There is no overlap or ambiguity in their purposes.
Tool names are all imperative verbs ('book', 'discover_businesses', 'get_business'). Two follow the verb_noun pattern, while 'book' is a standalone verb, but the style is consistent and clear.
With 3 tools, the set is compact but well-scoped for a booking gateway. It provides the essential actions (discover, retrieve, book) without redundancy, though it is on the minimal side.
The tools cover the full user journey: searching for businesses, examining details, and initiating a booking. There are no obvious dead ends, and the scope is clearly defined by the booking gateway purpose.