Skip to main content
Glama
Sign In
bugezy

bugezy

by fox100039-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_voice_transcript

Retrieve the developer's voice transcript from a bug report by providing the report ID. This transcription offers key debugging clues.

Instructions

取得開發者的語音描述（中文轉錄）— 通常是最有價值的除錯線索。Get developer voice transcript — often the most valuable debugging clue.

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": {
      "report_id": "<report_id>"
    },
    "name": "get_voice_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYes報告 ID（report_id）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior fully. It only states what the tool does without mentioning authentication needs, return format, potential failures, or side effects. Minimal behavioral context.

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

Conciseness5/5

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

Two short sentences (bilingual) convey purpose and value with zero wasted words. Essential information is front-loaded.

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?

For a tool with no output schema, the description should at least hint at the response structure (e.g., transcript text). It does not, leaving the agent uncertain about what to expect. Additionally, it doesn't connect to prerequisite data like report_id, which is likely from list_reports.

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% for the single parameter 'report_id', so the schema already defines it. The description adds no additional meaning or format guidance beyond the schema.

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 retrieves a developer's voice transcript, using specific verbs ('get') and resources ('voice transcript'). It distinguishes itself from sibling tools like get_console_logs or get_network_errors by focusing on a unique data type.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description hints at usage by calling it 'the most valuable debugging clue,' implying priority over siblings. However, it does not explicitly state when to use it vs. alternatives or provide exclusion criteria.

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