Skip to main content
Glama

can_send_image

Read-only

Checks whether the current QQ account can send images, helping you verify image-sending capability before attempting to send one.

Instructions

can_send_image 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_image"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 safe-query profile is known. The phrase 'capability query result' is consistent with that but adds little beyond it: no mention of what is checked, latency, whether results are cached, or what a false result implies.

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

Conciseness2/5

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

Very short, but structurally poor: it opens by repeating the tool name verbatim, then an English label 'Returns:' followed by an untranslated Chinese fragment. It is terse without being informative rather than concise.

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?

No output schema exists, so the description is the only place the return value could be characterized, and 'capability query result' does not say whether the result is a boolean, an object with reason codes, or per-image-type granularity. For a simple zero-arg predicate call this is a meaningful gap.

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?

There are zero parameters so there is nothing for the description to disambiguate. The schema does allow additionalProperties, which the description does not clarify, keeping it from a higher score.

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

Purpose3/5

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

The description mostly restates the name, but the fragment "Returns: 能力查询结果" (capability query result) does signal that this is a capability check rather than an action. It never says what capability is being checked (permission, connectivity, format support) or how it differs from siblings like send_image or can_send_record.

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 when-to-use or when-not-to-use guidance is given, and no relationship to send_image is stated (e.g. 'call before send_image to check whether the send will succeed'). The agent must infer the pre-flight-check role from the name alone.

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