Skip to main content
Glama

通用图像理解

image_analysis

Analyze images, videos, and screenshots to answer questions. Provides structured descriptions and responses based on visual input.

Instructions

通用兜底:理解任意图片并回答问题。不确定用哪个专用工具,或只是想问一张图时使用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYes图片:本地路径 / file:// / http(s):// / data: URI
questionNo具体问题或额外要求
detail_levelNo细节级别:overview=单次快速;normal/fine/auto 触发由粗到细的自动缩放(auto 为默认,足够清晰则早退)
regionNo可选:手动指定关注区域,命名如 'top-right' 或归一化 bbox 'x,y,w,h'(0~1)
thinkingNo是否开启视觉模型深度推理(默认按工具/后端策略)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownYes人类可读的结构化 markdown 正文(与 content 一致)
confidenceNo模型对结果的置信度
roundsYes实际经历的视觉调用轮数
regionsNo缩放走过的区域轨迹(归一化 bbox)
warningsYes降级/截断/不确定等告警
providerYes
modelYes
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It discloses the tool's purpose but omits behavioral details such as response format, latency, or any constraints. A brief note on capabilities or limitations would improve transparency.

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?

The description is very concise (one sentence) and front-loads the purpose. However, it could benefit from slight restructuring to separate the fallback role from the usage instruction.

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?

Given the presence of sibling tools and an output schema, the description adequately establishes the tool as a fallback. It could be more complete by explicitly noting that for specific tasks (e.g., data visualization), specialized tools are preferred.

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 coverage is 100%, so parameters are already well-documented. The description does not add significant meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

The description explicitly states it is a general fallback for understanding any image and answering questions. It clearly distinguishes itself from sibling tools by positioning as a catch-all when unsure which specialized tool 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 Guidelines5/5

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

The description provides explicit guidance: use when uncertain about which dedicated tool to pick or when you just want to ask about an image. This directly addresses selection criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pelican0126/vision-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server