Look up a single business on Yelp by alias or encoded ID via Yelp's real Android app backend. Returns details without requiring login, API key, or cookies.
Get Yelp business detail. Looks up a single Yelp business by alias or encoded id via Yelp's real Android app backend. Credential-free: no login, no API key, no cookie required from the caller.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Yelp business alias or encoded id |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It meaningfully discloses the credential-free access and the underlying Android app backend, adding valuable context beyond the schema. It doesn't cover error cases or return format, but the simple read-only nature is evident.
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?
Three short sentences, front-loaded with the main purpose. Each sentence adds a distinct useful detail: single business, backend source, and credential requirements. No waste.
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 tool is simple with one parameter and no output schema. The description adequately covers the purpose, parameter, and auth expectations, enough for an agent to select and invoke it. It could optionally mention how to obtain the id via yelp_search, but this is not essential.
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 100% and the only parameter 'id' already has a description. The tool description reinforces that the id can be an alias or encoded id but adds no new format details or examples beyond the schema.
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 uses a specific verb ('looks up') and clearly identifies the resource ('single Yelp business by alias or encoded id'). It distinguishes this tool from siblings like yelp_search and yelp_business_reviews.
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?
It provides clear context that this tool is for retrieving business detail, which implies when to use it. It doesn't explicitly mention exclusions or alternatives, but the scope is obvious from the description and sibling tool names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.