Skip to main content
Glama

fetch_ptt_text

Read-only

Retrieves speech-to-text results for QQ voice messages by message ID, returning the recognized text. Use a real message_id from a message event or send result; negative values are valid.

Instructions

获取语音转文字结果 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。 Returns: { text }:语音识别出的文本。

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": {
      "message_id": "<message_id>"
    },
    "name": "fetch_ptt_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds non-obvious behavior: negative message_id values are accepted, and the call only succeeds if the message exists in the current account's store. It also discloses the return shape ({ text }). It does not describe failure behavior when the message is absent, which is the remaining gap.

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?

Four compact clauses plus a return-value note, with the core action front-loaded. Every clause carries information (source of id, negative-value rule, storage precondition, return shape). The clauses run together without clear separators, slightly hurting scannability.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, the description covers the identifier's origin, its edge-case validity, the lookup precondition, and the return value. That is nearly everything an agent needs to invoke it correctly; only the not-found/failure outcome is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema only constrains message_id to integer|string with 'not 0', so the description must carry the meaning — and it does, explaining that the value must be a real message_id from a message event or send result and that negative values are valid. That directly clarifies the otherwise cryptic 'not: const 0' constraint. Minor gap: nothing about string-formatted ids versus integers.

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 opens with a specific verb+resource pair ('获取语音转文字结果') that unambiguously identifies the operation as retrieving an ASR transcript for a message. It does not name or contrast any sibling tool, so the reader must rely on the name to distinguish it from other fetch_* tools, but the resource is distinctive enough that confusion is unlikely.

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

Usage Guidelines4/5

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

It tells the agent exactly where the required identifier comes from ('消息事件或发送结果中的真实 message_id') and states the precondition that the message must be queryable in the current account's message store, which is genuine when-to-use context. It stops short of explicit exclusions or naming an alternative tool for cases where the precondition fails.

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