Skip to main content
Glama

Inspect an image

inspect_image
Read-onlyIdempotent

Facts about an image without changing it: format, dimensions, file size, colour space, transparency, which hidden metadata it carries (EXIF, GPS position, colour profile), camera details, and fingerprints for finding duplicates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlNoPublic http(s) address of the image. Use this or image_base64.
image_base64NoThe image file's bytes, base64-encoded. Use for a local file, e.g. one in the repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description earns credit beyond that by disclosing what data the call exposes — notably hidden EXIF, GPS coordinates, and colour profile — which tells the agent this can surface privacy-sensitive information that other tools would strip. It says nothing about failure modes for unreachable URLs or about rate limits.

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?

A single front-loaded sentence: the read-only guarantee comes first, followed by a tight enumerated list of outputs. No filler, no repetition of the title, and every clause carries information an agent can act on.

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 two-parameter read-only tool with full schema coverage and no output schema, the description usefully substitutes for the missing return definition by naming the metadata categories returned. The remaining gap is the mutually-exclusive-but-both-optional input pair, which neither the schema nor the description resolves.

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 documented in-schema, so this is the baseline case. The description adds no parameter-level meaning and, importantly, does not state that exactly one of the two inputs should be supplied — a real ambiguity given that required parameters is 0 and there is no oneOf constraint.

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 opens with a specific operation and resource ('Facts about an image without changing it') and enumerates exactly what is returned: format, dimensions, colour space, EXIF/GPS metadata, camera details, and duplicate fingerprints. That is far more concrete than the bare title 'Inspect an image'. It does not name any sibling explicitly, so differentiation from compress_image/convert_image is only implied by 'without changing it'.

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 implied rather than stated: 'without changing it' signals this is the non-mutating path versus its transform siblings, and 'fingerprints for finding duplicates' hints at a dedupe workflow. There is no explicit when-to-use, when-not-to-use, or named alternative, and no guidance on choosing between image_url and image_base64.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources