Skip to main content
Glama

analyze_image

Analyze images using AI vision to generate descriptions, alt text, tags, semantic analysis, or OCR text—supporting accessibility, content management, and searchable image organization.

Instructions

Analyze images using AI vision to generate descriptions, alt-text, tags, or detailed semantic analysis.

Use this when:

  • Generating accessible alt-text for images

  • Creating image descriptions for content management

  • Auto-tagging images for organization and search

  • Getting detailed semantic analysis of image content

  • Extracting text from images (OCR)

NOT for:

  • Generating new images (use generate_image instead)

  • Editing or modifying images (use edit_image instead)

  • Removing backgrounds (use remove_background instead)

Example: "analyze_image imagePath='/path/to/photo.jpg' analysisType='description'"

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": {
      "imagePath": "<imagePath>",
      "analysisType": "<analysisType>",
      "extractText": "<extractText>",
      "includeModeration": "<includeModeration>",
      "model": "<model>",
      "skipCache": "<skipCache>",
      "timeout": "<timeout>"
    },
    "name": "analyze_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesgemini-3-flash
contextNo
focusOnNo
timeoutYes
imagePathYes
skipCacheYes
extractTextYes
analysisTypeYesdescription
analysisTypesNo
outputFilenameNo
includeModerationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing about cost/latency, caching (a skipCache parameter exists and its effect is never explained), whether an output file is written via outputFilename, or what moderation results look like. It also doesn't say whether the operation is read-only or has side effects — non-trivial given the file-writing parameter.

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?

Front-loaded with the core capability, then scannable when/when-not lists, then a concrete example — good structure with no filler sentences. The bullet lists are slightly long but each entry adds routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, 7-required tool with zero annotation coverage and no output schema, the description leaves too much unexplained: the required-but-defaulted parameters (model, timeout, skipCache, extractText, includeModeration) and their effects on cost and output are unaddressed. It adequately describes what the tool does but not how to invoke it correctly beyond the minimal example.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, so the description must compensate, and it only illustrates imagePath and analysisType in the example. Eight parameters — model, context, focusOn, timeout, skipCache, analysisTypes (plural vs. singular analysisType is never disambiguated), outputFilename, includeModeration — get no meaning from either source.

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?

States a specific verb and resource ("Analyze images using AI vision") and enumerates the four output modes (descriptions, alt-text, tags, detailed semantic analysis). The NOT-for section explicitly separates it from generate_image, edit_image, and remove_background, so an agent can distinguish it from siblings without opening the schema.

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?

Provides an explicit 'Use this when' list of five concrete scenarios (alt-text, descriptions, tagging, semantic analysis, OCR) plus a 'NOT for' list that names the correct alternative tool for each excluded case. This is the strongest form of routing guidance.

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