search_studiosFind bookable craftsperson studios on CraftMe near a location or in a city, nearest first. Optionally only studios with a matching service.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City name, used when no coordinates are known | |
| limit | No | Max studios, default 10, at most 20 | |
| latitude | No | ||
| longitude | No | ||
| radius_km | No | Search radius around the coordinates, default 25 | |
| service_query | No | Words the service name must contain, e.g. "electrician" |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds a genuinely useful behavioral fact: results are ordered nearest-first. It does not disclose pagination/truncation behavior beyond the schema's limit, or how it behaves when coordinates are absent, 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with what is returned and how it is ordered, then the optional filter. No filler.
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 six-parameter, all-optional lookup with no output schema, the description covers the essential intent, search modes and ordering. The remaining gaps (result shape, behavior with no location arguments, limit truncation) are minor for a search tool.
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 coverage is 67% and latitude/longitude carry no descriptions at all; the description only loosely signals the location-vs-city choice and that service_query is an optional substring match. It adds a little meaning over the schema but does not compensate for the undocumented coordinate pair or the interaction between city and coordinates.
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?
States a specific verb and resource ('Find bookable craftsperson studios'), the platform, and the ordering ('nearest first'), plus an optional filter. It is clearly distinct from get_studio (single studio) and prepare_booking, though it never names those siblings explicitly.
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?
'near a location or in a city' implies the two search modes and the description hints the service filter is optional, but there is no explicit when-to-use guidance, no mention of when to prefer find_free_slots or get_studio, and no statement about what happens when neither city nor coordinates are supplied.
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.