lookup_dog_breed
Get info + image for a dog breed. Use for pet content agents.
Example call: {"breed": "shiba"}
Cost: $0.005–$0.05 USDC on Base per call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| breed | Yes |
Get info + image for a dog breed. Use for pet content agents.
Example call: {"breed": "shiba"}
Cost: $0.005–$0.05 USDC on Base per call.
| Name | Required | Description | Default |
|---|---|---|---|
| breed | Yes |
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?
No annotations provided, so description must disclose behaviors. It mentions cost per call, but does not disclose side effects, speed, rate limits, or response format beyond 'info + image'.
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?
Very concise with three short sentences, an example, and cost info. No wasted words, though could be better structured with sections.
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?
No output schema or annotations. Description provides basic purpose and cost, but lacks details on return format, limitations, or data freshness. Adequate but not rich.
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?
Single required parameter 'breed' with no schema description (0% coverage). Description provides an example ('shiba') but no valid values, case sensitivity, or formatting rules.
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 'Get info + image for a dog breed' with a verb and resource. It is distinct from sibling lookup_* tools by focusing on dog breeds, but does not explicitly differentiate from them.
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?
Only suggests 'Use for pet content agents.' No guidance on when not to use or alternatives among many similar lookup tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.