Skip to main content
Glama
Sign In
GoldBean

GoldBean

by wuzenghai616-lang
OverviewSchemaSourceRelated ServersDiscussions(4)Admin
JavaScript
Remote

baidu_ocr

Extract text from images using a provided URL. Returns recognized text with high accuracy.

Instructions

[OCR] 通用文字识别（高精度版） — $0.01/call (free: 5/5 today)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image": "<image>"
    },
    "name": "baidu_ocr"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYes图片URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as required authentication, input constraints, output format, or side effects. The description only states pricing.

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

Conciseness2/5

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

The description is extremely brief but under-specified. While it is concise, it fails to provide necessary context, making it inadequate for the tool's complexity.

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

Completeness1/5

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

Given the tool has one parameter, no output schema, and many similar siblings, the description is severely incomplete. It lacks details on return values, image format requirements, and use cases.

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?

The input schema has one parameter 'image' with a description '图片URL', achieving 100% schema coverage. The tool description does not add any additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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

Purpose2/5

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

The description is a label in Chinese ('通用文字识别（高精度版）') with pricing, but does not clearly state the tool's function in English. It vaguely implies general text recognition but does not distinguish it from the many other OCR sibling tools.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of appropriate use cases, limitations, or exclusions.

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

Deploy Server

Other Tools