Skip to main content
Glama
RunhuaHuang

VisionPower

by RunhuaHuang
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Describe Image

describe_image

Analyze images to extract text, describe scenes, compare visuals, and answer questions from screenshots, photos, diagrams, or charts. Provide the image by path, URL, or base64 for direct answers.

Instructions

See and understand images — screenshots, photos, diagrams, charts. Extract text (OCR), describe scenes, compare images, and answer questions about what is shown. Use whenever an image is provided via image_path, image_url, image_base64, image_ref, or images[]. For faster, more useful answers, ask the specific question you need answered (e.g. "read the error text", "what does this chart show") instead of an open-ended "describe everything".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNoOrdered list of images to analyze. Use this for multiple images; do not combine it with top-level image fields.
promptNoSpecific question or instruction about the image(s). Focused questions (e.g. "Read the error message text", "List the visible menu items") are faster and more useful than open-ended "describe everything" prompts. Leave empty for a full description.
image_refNoShort-lived opaque reference created by the VisionPower WebUI Inbox. Use this when a text-only host cannot pass an attachment through to the agent.
image_urlNoPublic http(s) URL of an image; support depends on the configured provider/model. Use image_base64 or image_ref when URL input is unavailable.
image_pathNoAbsolute path to a local raster image file. Use this when the image is available on disk.
image_base64NoBase64-encoded image data without a data: URI prefix.
output_formatNoOutput shape. 'text' (default) returns a free-form description with an untrusted-source banner. 'structured' returns a JSON envelope: when formatValid is true, a single image has {answer, observations, extractedText?, limitations?} and multiple images have images[]; otherwise formatValid is false with formatError and rawResponse.
image_mime_typeNoMIME type for image_base64. If omitted, VisionPower detects it from image bytes.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv3.1.1
    • addedInput schema / properties / image_ref
      Added value: +{
+  "description": "Short-lived opaque reference created by the VisionPower WebUI Inbox. Use this when a text-only host cannot pass an attachment through to the agent.",
+  "pattern": "^vpimg_[A-Za-z0-9_-]{32}$",
+  "type": "string"
+}
    • changedInput schema / properties / image_url / description
      Previous value: -"Public http(s) URL of an image that the configured vision model provider can access."New value: +"Public http(s) URL of an image; support depends on the configured provider/model. Use image_base64 or image_ref when URL input is unavailable."
    • addedInput schema / properties / images / items / properties / image_ref
      Added value: +{
+  "description": "Short-lived opaque reference created by the VisionPower WebUI Inbox. Use this when a text-only host cannot pass an attachment through to the agent.",
+  "pattern": "^vpimg_[A-Za-z0-9_-]{32}$",
+  "type": "string"
+}
    • changedInput schema / properties / images / items / properties / image_url / description
      Previous value: -"Public http(s) URL of an image that the configured vision model provider can access."New value: +"Public http(s) URL of an image; support depends on the configured provider/model. Use image_base64 or image_ref when URL input is unavailable."
    • changedInput schema / properties / prompt / description
      Previous value: -"Specific question or instruction about the image(s). Leave empty for a full description."New value: +"Specific question or instruction about the image(s). Focused questions (e.g. \"Read the error message text\", \"List the visible menu items\") are faster and more useful than open-ended \"describe everything\" prompts. Leave empty for a full description."
  2. Changed1 schema field changedv2.4.2
    • addedInput schema / properties / output_format
      Added value: +{
+  "description": "Output shape. 'text' (default) returns a free-form description with an untrusted-source banner. 'structured' returns a JSON envelope: when formatValid is true, a single image has {answer, observations, extractedText?, limitations?} and multiple images have images[]; otherwise formatValid is false with formatError and rawResponse.",
+  "enum": [
+    "text",
+    "structured"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changedv2.3.0
    • changedInput schema / properties / image_mime_type / enum
      Previous value: -[
-  "image/jpeg",
-  "image/png",
-  "image/webp",
-  "image/gif",
-  "image/bmp"
-]New value: +[
+  "image/jpeg",
+  "image/png",
+  "image/webp",
+  "image/gif",
+  "image/bmp",
+  "image/tiff"
+]
    • changedInput schema / properties / images / items / properties / image_mime_type / enum
      Previous value: -[
-  "image/jpeg",
-  "image/png",
-  "image/webp",
-  "image/gif",
-  "image/bmp"
-]New value: +[
+  "image/jpeg",
+  "image/png",
+  "image/webp",
+  "image/gif",
+  "image/bmp",
+  "image/tiff"
+]
  4. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations only include openWorldHint=true, leaving the description with the main burden. It mentions provider dependency for image_url ('support depends on the configured provider/model') and hints at performance with focused prompts, but does not disclose potential limitations (e.g., image size, errors, or untrusted-source banner details). No contradiction with annotations, but limited behavioral disclosure.

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?

The description is a single, tight paragraph with no filler. It front-loads the core purpose and then gives practical usage tips. Slightly dense but efficient.

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?

Given the tool's complexity (8 parameters, no output schema), the description outlines capabilities and gives usage guidance but does not explain return formats (except via schema) or edge-case behavior. Since the schema covers parameter details and output_format, this is adequate but not rich. Missing information about size limits or error handling keeps it at a 3.

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 the baseline is 3. The description adds minimal extra meaning: it emphasizes focused prompts and repeats schema guidance for image input methods (e.g., 'Use image_base64 or image_ref when URL input is unavailable'). It does not significantly enhance parameter understanding beyond the schema.

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 the tool's purpose with specific verbs and resources: 'See and understand images — screenshots, photos, diagrams, charts. Extract text (OCR), describe scenes, compare images, and answer questions about what is shown.' It distinguishes from alternatives by listing the input methods and capabilities.

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?

Explicitly states when to use: 'Use whenever an image is provided via image_path, image_url, image_base64, image_ref, or images[].' Also provides guidance on how to phrase prompts for better results ('ask the specific question... instead of an open-ended...'), which is actionable usage direction.

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/RunhuaHuang/VisionPower'

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