Skip to main content
Glama

send_image

Send images to QQ groups or private contacts using the Amadeus-QQ-MCP server. Upload base64-encoded images to monitored groups or whitelisted friends with optional message replies.

Instructions

Send an image to a monitored group or whitelisted friend.

Args: target: Group ID or friend QQ ID. image: Base64-encoded image data (without the base64:// prefix). target_type: "group" (default) or "private". reply_to: Optional message ID to reply to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYes
imageYes
target_typeNogroup
reply_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Provides behavioral details (monitored group/whitelisted friend, base64 format without prefix) but no annotations exist. Lacks disclosures on permissions, rate limits, or failure behavior.

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 sentences front-load purpose, followed by parameter list. No wasted words, efficient structure.

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?

Covers parameters adequately but lacks details on return value, error handling, file size limits, and exact encoding validation. Acceptable for simple tool but gaps remain.

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?

With 0% schema coverage, description adds essential meaning: target is ID, image base64 encoding, target_type default/options, reply_to optional. Compensates well for missing schema descriptions.

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?

Description clearly states verb 'send' and resource 'image', and distinguishes from siblings like send_message, send_file, send_voice by specifying image-specific details.

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?

Implies usage for sending images to groups or friends, but lacks explicit when to use vs alternatives like send_message with image attachment, and no when-not scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.