Skip to main content
Glama

image_analyze

Analyze images from URLs or local paths to extract metadata, hashes, EXIF/GPS, dominant colors, OCR text, QR codes, and reverse-image search links locally without uploading.

Instructions

Analyze an image from a URL or local path.

Returns dimensions/format, hashes (MD5/SHA256/dHash/aHash), EXIF and GPS, dominant colors, OCR text (Tesseract), QR codes (OpenCV) and reverse-image search links for remote images. No upload; everything runs locally.

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": {
      "target": "<target>"
    },
    "name": "image_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrNo
ocrNo
targetYes
reverse_searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value: "No upload; everything runs locally" is a privacy/execution trait unavailable in structured fields, and the named engines (Tesseract, OpenCV) hint at processing cost. However, it omits failure modes (invalid path, unreachable URL), size/format limits, and does not clarify that reverse_search only yields links for remote images and cannot function on local paths.

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 input scope is front-loaded in the first sentence and the output inventory follows in a compact list; every clause conveys new information with no restatement of the tool name or filler.

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 four-parameter, no-annotation tool with no output schema, describing the returned fields is the right compensating move and is done well. Remaining gaps are behavioral edges (error handling, remote-vs-local constraints on reverse search) rather than structural ones.

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% for four parameters, so the description must compensate; it partially does by tying target to "URL or local path" and by connecting OCR, QR, and reverse-image search to the listed outputs, implicitly revealing what the three booleans toggle. It never names those toggles, states their defaults, or warns that disabling them changes the returned payload.

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?

States a concrete verb and resource ("Analyze an image from a URL or local path") and then enumerates the specific analyses produced (hashes, EXIF/GPS, dominant colors, OCR, QR, reverse search), which implicitly separates it from the narrower image_exif sibling. It stops short of naming any sibling explicitly, so differentiation is inferential rather than stated.

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?

Usage is only implied: an agent can infer this is the general-purpose image inspector, but nothing says when to prefer it over image_exif or how it relates to the case_image_* tools. There are no exclusions, prerequisites, or conditions selecting among alternatives.

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