Skip to main content
Glama
Sign In
Hydra Vision MCP

Hydra Vision MCP

by carlory
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_image

Interpret any image, screenshot, or visual when specialized tools do not fit. Provide a prompt and image source to extract or understand content.

Instructions

General-purpose image analysis for scenarios not covered by specialized tools.

Use this tool as a FALLBACK when none of the other specialized tools (ui_to_artifact, extract_text_from_screenshot, diagnose_error_screenshot, understand_technical_diagram, analyze_data_visualization, ui_diff_check) fit the user's need.

This tool provides flexible image understanding for any visual content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_source": "<image_source>",
      "prompt": "<prompt>"
    },
    "name": "analyze_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesDetailed description of what you want to analyze, extract, or understand from the image. Be specific about your requirements.
image_sourceYesLocal file path or remote URL to the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden of disclosure. It accurately describes a read-only analysis tool and mentions flexibility, but does not disclose output format, limitations, or error behavior. This adds some context but leaves gaps common for analysis tools.

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?

The description is concise, with two short sentences that front-load the purpose and usage. It includes a list of siblings but keeps it compact and relevant. Every sentence earns its place without bloat.

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?

The description sufficiently covers the fallback context and general capabilities. Given the simplicity of the tool (2 params, no output schema), it does not need to explain return values. It could mention limitations of the fallback nature, but overall it is complete enough for effective 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%, and both parameters are well-described in the schema. The tool description itself adds no extra parameter-specific meaning beyond noting the tool's general purpose. Baseline for full schema coverage is 3.

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 clearly states this is a general-purpose image analysis tool, with a specific verb ('analyze') and resource ('image'). It explicitly lists sibling tools, distinguishing itself as a fallback rather than a specialized handler, which makes its purpose unmistakable.

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 gives explicit usage guidance: 'Use this tool as a FALLBACK when none of the other specialized tools... fit the user's need.' It names the alternatives, making the selection criteria very clear.

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