Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_image_meta_inspector

Inspect a remote image header to retrieve its format, dimensions, animation, alpha, file size, and content type for validation or processing.

Instructions

[Dynamic Media] Inspect a remote image: format, dimensions, animation, alpha, size and content type from the file header Measured p50 12 ms, p95 42 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://media.caelaralabs.com.

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": "caelara_media_image_meta_inspector"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesImage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description does real work: 'from the file header' implies a partial fetch rather than a full download, and it discloses the outbound network dependency on media.caelaralabs.com plus measured latency (p50 12 ms, p95 42 ms). Missing are failure behavior for unreachable/hotlink-protected URLs, size limits, and whether the target URL is logged.

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 action and the returned fields, then network/latency facts. Every clause is relevant, though the benchmark date and citation URL are the least load-bearing element and could be trimmed without loss.

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?

There is no output schema, so the enumerated return fields (format, dimensions, animation, alpha, size, content type) are essential and present. For a one-parameter read-only inspector this is nearly sufficient; the remaining gap is error/edge-case behavior, which matters given it fetches arbitrary remote 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% and the single 'url' parameter is documented in-schema, so the baseline applies. The description adds only mild meaning by stressing 'remote' and naming the service host, implying the URL must be externally fetchable — useful, but not a substantive expansion of parameter semantics.

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 and resource ('Inspect a remote image') and enumerates exactly what is extracted: format, dimensions, animation, alpha, size, content type. The 'from the file header' qualifier sharpens scope nicely. It does not, however, distinguish itself from near-neighbors like caelara_media_aspect_ratio_calc or caelara_media_color_palette_extractor, which also touch image metadata.

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: you have an image URL and want header-level facts about it. There is no statement of when to prefer this over sibling tools that derive ratio or palette data, and no prerequisites such as the URL being publicly reachable or HTTP(S)-only.

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

Deploy Server

Other Tools