Skip to main content
Glama
Sign In
GoldBean

GoldBean

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

baidu_asr

Transcribe audio files to text using Baidu speech recognition. Provides accurate speech-to-text conversion from audio URLs.

Instructions

[Voice] 语音转文字（ASR） — $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": {
      "audioUrl": "<audioUrl>"
    },
    "name": "baidu_asr"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioUrlYes音频文件URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description shoulders burden. It does not disclose latency, supported languages, audio format restrictions, or limits beyond the free quota. Minimal behavioral info.

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 a single line, front-loaded with the key purpose. It includes pricing info, which may be useful, but no extraneous content. Efficient but could be more informative.

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

Completeness3/5

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

No output schema exists, and the description does not mention return format (text, confidence) or error handling. For a simple 1-parameter tool, this is minimally adequate but lacks completeness for an agent.

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 description coverage is 100%, so the schema already documents the audioUrl parameter. The description adds no extra meaning (e.g., accepted formats, max size). Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool converts voice to text using '[Voice] 语音转文字（ASR）', which is a specific verb+resource. Among sibling tools, no other ASR tool exists, so it distinguishes well.

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 alternatives. The description only mentions pricing and free quota, but no context about usage scenarios 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