Skip to main content
Glama

Diagnose Error Screenshot

diagnose_error_screenshot
Read-only

Submit an error screenshot to receive likely cause, actionable fixes, and prevention notes.

Instructions

Diagnose screenshots of error messages, stack traces, exception dialogs, or failed command output.

Returns likely cause, actionable fixes, and prevention notes where possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of what needs diagnosis in the error screenshot.
contextNoOptional context about when or where the error occurred.
image_detailNoOptional Codex Responses input_image detail. Defaults to CODEX_VISION_IMAGE_DETAIL or high.
image_sourceYesLocal file path, remote URL, or data:image URL to the error screenshot.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
errorNo
successYes
metadataNo
Behavior3/5

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

Annotations already declare readOnlyHint and destructiveHint, so agent knows it is safe. The description adds the output format but does not elaborate on behavioral traits like external API calls or processing time, which are hinted by openWorldHint.

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 concise sentences front-load purpose and output summary without wasted words. Every sentence adds value.

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?

Description covers input types and output summary. Given the openWorldHint and optional image_detail parameter, additional context about processing time or image requirements would improve completeness. Output schema exists, so return format is covered.

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 the schema already documents all parameters. The description does not add further semantic guidance for parameters, so baseline score of 3 applies.

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 uses the specific verb 'Diagnose' targeting error-related screenshots, listing input types (error messages, stack traces, etc.) and output types (cause, fixes, prevention). It clearly distinguishes from sibling tools like analyze_image (general) and extract_text_from_screenshot (text extraction).

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 implies usage for error screenshots but does not explicitly state when not to use it or reference alternative tools for non-error images. It lacks explicit when-to-use and when-not-to-use guidance.

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/darkamenosa/codex-vision-mcp'

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