baidu_animal
Identify animal species from a provided image URL using vision AI.
Instructions
[Vision] 动物识别 — $0.02/call (free: 5/5 today)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| image | Yes | 动物图片URL |
Identify animal species from a provided image URL using vision AI.
[Vision] 动物识别 — $0.02/call (free: 5/5 today)
| Name | Required | Description | Default |
|---|---|---|---|
| image | Yes | 动物图片URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only mentions pricing ($0.02/call, 5 free today). It discloses no behavioral traits such as whether the tool is read-only, destructive, or has rate limits. This is critically lacking.
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 extremely concise (one line), which is positive for brevity, but it omits essential information. It lacks structured details such as what the output contains or constraints on input images.
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?
Given the simple schema and no output schema, the description should provide thorough context about what the tool returns (e.g., animal species, confidence scores). It fails to do so, leaving the agent without adequate information to assess utility.
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 has 100% coverage with a single parameter 'image' described as '动物图片URL'. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.
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 includes '[Vision] 动物识别' which clearly indicates this tool recognizes animals from images. However, it does not differentiate from sibling vision tools like baidu_object_detect or baidu_plant, but the name itself is sufficiently specific.
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 provides no guidance on when to use this tool versus alternatives. For example, it does not mention that this tool is for animal recognition specifically or suggest other tools for different object categories.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wuzenghai616-lang/goldbean'
If you have feedback or need assistance with the MCP directory API, please join our Discord server