Skip to main content
Glama

can_send_record

Read-only

Checks whether the connected QQ account can send voice messages, helping avoid failed send attempts.

Instructions

can_send_record Returns: 能力查询结果。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "can_send_record"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing beyond that: it does not say whether the result depends on account state, permissions, target context, or external service availability, despite openWorldHint implying external dependence. The mixed-language "Returns:" fragment conveys no behavioral content.

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

Conciseness3/5

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

It is extremely short, so there is no padding, but it is not front-loaded with useful information either. The "Returns:" label is an odd half-fragment that mixes English and Chinese and conveys no actual return detail, which is wasted structure rather than concise signal.

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

Completeness1/5

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

For a capability-query tool with no output schema, the description must explain what the returned result means and how to interpret a true/false or capability payload, and it does not. It also fails to define the scope of "record," leaving an agent unable to act on the answer even if it received one.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline of 4 applies. The permissive schema with additionalProperties=true is not explained, but no parameters exist to document.

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

Purpose2/5

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

The description restates the tool name ("can_send_record") and appends only "Returns: 能力查询结果" ("capability query result"), which is a tautology rather than a statement of what is actually checked. It never says what "record" refers to, which sending channel is involved, or whose capability is being queried, so an agent cannot distinguish it from siblings like send_msg or can_send_image on the basis of this text.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or when the check should be skipped. With siblings such as send_msg and send_group_msg in the catalog, the definition offers nothing to help choose this pre-flight check over simply attempting a send.

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