Skip to main content
Glama

Detect Objects in Image

detect_objects_in_image

Detect objects in images using AI vision models and get annotated images with bounding boxes. Accepts URLs, base64 data, or file paths.

Instructions

Detect objects in an image using AI vision models and generate annotated images with bounding boxes. Supports URLs, base64 data, and local file paths. File handling: explicit filePath → exact path, otherwise → temp directory. Uses optimized default parameters for object detection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesText prompt describing what to detect or recognize in the image. Avoid including any instructions about output structure or formatting — these are automatically managed by the workflow.
imageSourceYesImage source - can be a URL, base64 data (data:image/...), or local file path
viewportWidthNoOptional logical viewport width (for web screenshots). Used to distinguish between actual image dimensions and logical viewport size.
outputFilePathNoOptional explicit output path for the annotated image. If provided, the image is saved to this exact path. Relative paths are resolved against the MCP server's current working directory.
viewportHeightNoOptional logical viewport height (for web screenshots). Used to distinguish between actual image dimensions and logical viewport size.
Behavior3/5

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

With no annotations, the description partially compensates by disclosing file handling behavior (explicit path vs. temp directory) and use of default parameters. However, it does not cover permissions, rate limits, or result format details.

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 concise (three sentences) and front-loaded with the main purpose. It efficiently covers key points without unnecessary verbosity.

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 5 parameters and no output schema or annotations, the description adequately explains the tool's inputs and basic behavior. However, it lacks details about the return value (annotated image format), error handling, and performance characteristics.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds valuable context beyond the schema. For example, it advises against including output structure instructions in the prompt, explains viewport parameters for web screenshots, and details outputFilePath resolution.

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?

The description clearly states the tool detects objects and generates annotated images. It specifies supported image sources (URL, base64, file path). However, it does not differentiate from sibling tool 'analyze_image', which may have overlapping capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'analyze_image' or 'compare_images'. The description mentions 'optimized default parameters' but does not provide context for appropriate usage scenarios.

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/tan-yong-sheng/ai-vision-mcp'

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