Skip to main content
Glama

Caelara Labs Dynamic Media

image_meta_inspector

Inspect a remote image: format, dimensions, animation, alpha, size and content type from the file header

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": {
      "url": "<url>"
    },
    "name": "image_meta_inspector"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesImage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 disclosure burden, and it does add one genuinely useful detail: metadata is read from the file header, which tells the agent this is a lightweight inspection rather than a full download or decode. It does not disclose failure behavior for unreachable or non-image URLs, redirect handling, authentication requirements, or whether the remote file is fetched at all.

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?

One front-loaded sentence that leads with the action and resource, then lists the returned fields. No filler, no repetition of the tool name, nothing to trim.

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 one-parameter read-only tool with a fully documented schema and no output schema, the description is nearly sufficient: it enumerates return values, which substitutes for the missing output schema. The only gap is error behavior for bad or unreachable URLs.

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 coverage is 100% on the single 'url' parameter, so the baseline of 3 applies. The description only adds that the image must be remote, which slightly constrains acceptable URL values (no local paths) but adds no format or validation detail beyond the schema.

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 specific verb (inspect) and resource (remote image) and enumerates exactly what it returns: format, dimensions, animation, alpha, size and content type. It is clearly distinguishable from the sibling generators/calculators, though it does not explicitly say how it differs from the closest sibling, color_palette_extractor, which also reads an image.

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: 'remote image' signals that this is a metadata-reading tool for a URL rather than an image-producing one. There is no explicit when-to-use statement, no exclusion of local files or non-image URLs, and no pointer to alternatives for related needs such as color extraction or favicon resolution.

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