Skip to main content
Glama

get_image

Read-only

Retrieve image information from a QQ message segment using its file or file_id; the image must exist in the current account's media cache.

Instructions

获取图片信息 file 或 file_id 原样取自图片消息段,须在当前账号媒体缓存中存在。

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": "get_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
file_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is clear. The description adds useful context beyond the annotations: the source of the parameters and the media-cache prerequisite that can cause failures. It says nothing about what data is returned, though, which matters for a 'get info' tool.

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?

Two short clauses, front-loaded with the purpose, no filler. Minor loss: the density of the Chinese phrasing means some details (which of file/file_id to supply) are packed rather than clearly enumerated.

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 simple read-only lookup with 2 optional string parameters and no output schema, the description covers the essential preconditions an agent needs to invoke it successfully. The remaining gap, mainly the distinction between the two parameters and the returned content, is modest for this complexity level.

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 0%, so the schema alone does not explain the two optional parameters. The description clarifies where the values originate (a raw image message segment) and the cache precondition, which is genuinely additive. It still does not explain the difference between file (path/base64?) and file_id, or which to use when both are empty.

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 gives a specific verb and resource ("获取图片信息" / get image information) and adds a scope detail: the parameters come from an image message segment. It does not, however, distinguish this tool from siblings like view_image, ocr_image, or download_file_image_stream, so an agent must infer which one to use.

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 names a real prerequisite: file/file_id must be taken verbatim from an image message segment and the file must already exist in the current account's media cache. That implies usage when handling image messages, but it never states when to prefer this over view_image or download_file_image_stream, nor any exclusions.

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