Skip to main content
Glama
Sign In
GoldBean

GoldBean

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

baidu_ocr_handwriting

Transform handwritten images into editable text. Submit an image URL to perform OCR on handwriting.

Instructions

[OCR] 手写文字识别 — $0.02/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_handwriting"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYes图片URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

The description includes pricing ($0.02/call) and free quota (5/5 today), which are behavioral traits beyond what annotations would provide (none exist). However, it omits other behavioral details like supported languages, image requirements, or rate limits, so it is only partially transparent.

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

Conciseness4/5

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

The description is extremely concise, using a single line to convey purpose, pricing, and quota. No redundant information is present, and the bracket prefix '[OCR]' adds quick categorization. However, it could be slightly more structured with separate sentences.

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 no output schema, the description should explain return values but does not. It also lacks information on image format constraints, size limits, or language support. For a simple tool with one parameter, the description is incomplete, leaving the agent without critical usage context.

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 100% coverage for its single parameter 'image', which the description does not elaborate on further. With full schema coverage, the baseline is 3, and the description adds no additional meaning beyond the schema's '图片URL'.

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 clearly states the tool as handwriting OCR via the label '[OCR] 手写文字识别', indicating the specific resource and action. However, it does not explicitly differentiate from many sibling OCR tools like baidu_ocr or baidu_ocr_accurate, relying on the name 'handwriting' to distinguish.

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 vs alternatives such as baidu_ocr (general) or baidu_ocr_numbers. The description lacks context for ideal use cases or exclusions, leaving the agent to infer from the name alone.

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