baidu_ocr_seal
Extract text from seals in images using OCR. Recognizes seal impressions for verification or digitization.
Instructions
[OCR] 印章识别 — $0.02/call (free: 5/5 today)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| image | Yes | 图片URL |
Extract text from seals in images using OCR. Recognizes seal impressions for verification or digitization.
[OCR] 印章识别 — $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 states the tool's function and cost. It does not disclose behavioral traits such as input requirements, output format, or any side effects. The description carries the full burden for behavioral transparency but fails to add meaningful context beyond the obvious.
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 concise, fitting in a single line. It includes useful pricing and quota info without extra fluff. However, it could be better structured, e.g., separating pricing from purpose.
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 annotations and output schema, the description is insufficient. It does not explain return values, image format requirements, or any limitations, leaving significant gaps for the agent.
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 a 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 clearly states it's for seal/stamp recognition, using the Chinese term '印章识别', which is specific and distinguishes it from general OCR tools. The purpose is immediately understandable.
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 pricing and free quota info, which helps in cost-conscious decisions, but lacks explicit guidance on when to use this tool versus other OCR siblings (e.g., baidu_ocr, baidu_ocr_handwriting). No alternative names are mentioned.
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