Skip to main content
Glama

baidu_qianfan_ocr

Extract text from images using optical character recognition. Supports optional prompts and handles contexts up to 32k tokens.

Instructions

[OCR] Qianfan-OCR 32k上下文通用OCR — $0.02/call (free: 5/5 today)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYes图片URL
promptYes识别指令(可选)
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description mentions 'free: 5/5 today' indicating a daily usage limit, but does not disclose any other behavioral traits such as whether it modifies data, authentication needs, or rate limits beyond the free quota. No annotations exist to supplement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one line), which is concise but lacks structure. It packs the tool name, context size, and pricing into a single sentence, but misses the opportunity to organize information for quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and many sibling OCR tools, the description is incomplete. It does not explain the return format, supported image types, or how this OCR differs from others (e.g., baidu_ocr_handwriting, baidu_ocr_table).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions for both parameters are provided ('图片URL' and '识别指令(可选)'), so baseline is 3. The tool description adds no additional semantics to the parameters, such as format constraints or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the tool as an OCR tool with 'Qianfan-OCR 32k上下文通用OCR', clearly stating it performs optical character recognition. However, among many sibling OCR tools, it does not specify what makes it distinct (e.g., 32k context vs others).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 alternative OCR tools like baidu_ocr, baidu_ocr_accurate, baidu_vision_chat, etc. There is no mention of scenarios, prerequisites, or when to avoid.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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