Skip to main content
Glama
Sign In
GoldBean

GoldBean

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

baidu_idcard

Extract key information from Chinese ID cards using optical character recognition. Identify text fields such as name, ID number, and address from uploaded images.

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_idcard"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYes身份证图片URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description only mentions OCR and cost. It does not disclose image requirements, accuracy, or privacy implications, which is important for ID card processing.

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?

Very concise with a single line. Includes useful pricing info, but could benefit from structured format.

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?

Lacks output schema and behavioral details. For a simple OCR tool, it misses context on return format and requirements.

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 covers 100% of parameters with description of 'image' as URL. The description adds no extra semantics beyond the schema.

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 'OCR ID card recognition' and includes a pricing hint. However, it does not elaborate on the specific type of ID card or distinguish from sibling OCR tools beyond the tag.

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 on when to use this tool vs other OCR tools like baidu_ocr or baidu_ocr_accurate. The agent is left to infer from the name and description.

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