baidu_logo
Identify logos from image URLs. Returns recognized logo names and details.
Instructions
[Vision] Logo识别 — $0.02/call (free: 5/5 today)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| image | Yes | Logo图片URL |
Identify logos from image URLs. Returns recognized logo names and details.
[Vision] Logo识别 — $0.02/call (free: 5/5 today)
| Name | Required | Description | Default |
|---|---|---|---|
| image | Yes | Logo图片URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose any behavioral traits such as read-only hint, error behavior, or response structure. With no annotations present, the tool's behavioral attributes are entirely unspecified beyond the basic function, which is insufficient for an AI agent to understand side effects or limitations.
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 very short, which is good for conciseness, but it mixes functional purpose with pricing information. The structure could be improved by separating pricing into annotations. Each sentence earns its place, but the inclusion of pricing in the description is somewhat misplaced.
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 lack of output schema and the simple nature of the tool, the description should inform about return values, confidence scores, or supported logo types. It provides only the basic function and pricing, leaving the agent underinformed about expected outputs.
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 only parameter 'image' is described in the schema as 'Logo图片URL', and the tool description adds no further meaning. Since schema description coverage is 100%, the baseline is 3. The description does not enhance understanding of the parameter beyond what the schema already provides.
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 explicitly states 'Logo识别' (Logo recognition), making the tool's purpose clear as recognizing logos from images. However, it does not differentiate from sibling vision tools like baidu_landmark or baidu_object_detect, so it lacks sibling differentiation. The inclusion of pricing is extraneous.
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?
No guidance is provided on when to use this tool versus alternatives. There are many sibling vision tools, but the description gives no context for selection, e.g., when to prefer logo recognition over object detection or landmark recognition.
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