Skip to main content
Glama

报错截图诊断

diagnose_error_screenshot

Diagnose software errors from screenshots by extracting root cause, exact error text, location, and fix steps.

Instructions

分析报错/异常截图,给出根因、逐字错误原文、位置和可执行的修复步骤。处理崩溃/红屏/堆栈截图时使用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYes图片:本地路径 / file:// / http(s):// / data: URI
code_contextNo相关代码/上下文,帮助定位
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
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits such as read-only nature, external API calls, or side effects. Only mentions outputs, not internal 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: first states functionality, second states when to use. No wasted words, front-loaded.

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?

Adequately covers purpose and usage context. With output schema present, return values are covered. Lacks mention of dependencies or prerequisites, but sufficient for selection.

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 100%, so baseline is 3. Description adds no extra parameter meaning beyond what schema already provides.

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 it analyzes error/exception screenshots, providing root cause, verbatim error text, location, and fix steps. Specifies to use for crash/red screen/stack screenshots, distinguishing from sibling tools like image_analysis.

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

Usage Guidelines4/5

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

Explicitly says 'use when dealing with crash/red screen/stack screenshots', giving clear context. Does not name alternatives but context implies differentiation from general image analysis tools.

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