Skip to main content
Glama
Sign In
mcp-image-tools

mcp-image-tools

by rog0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

image_metadata

Retrieve image metadata from a URL using HTTP headers—content type, size, last-modified, etag, cache info—without downloading the image.

Instructions

Read image metadata from a URL via HTTP headers: content-type, file size, last-modified, etag, cache info. No image downloading required.

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_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDirect URL to an image file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It explains that the tool works via HTTP headers and does not download images, but it does not mention potential edge cases like missing headers, redirects, or rate limits. This is adequate for a simple read operation but not comprehensive.

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?

The description is two short, focused sentences. It front-loads the action and enumerates specific metadata types without any redundant or vague wording.

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 tool with only one parameter and no output schema, the description effectively communicates what metadata will be returned and the method used. It lacks edge-case handling details, but is otherwise complete enough for an agent to invoke it correctly.

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?

The schema already fully describes the url parameter as 'Direct URL to an image file' (100% coverage). The description adds context about HTTP headers but does not further clarify the parameter itself, so a baseline 3 is appropriate.

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 reads image metadata from a URL via HTTP headers, listing specific fields like content-type, file size, and cache info. This definitively distinguishes it from siblings such as find_favicons or generate_placeholder.

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

Usage Guidelines4/5

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

The description implies usage for fetching metadata without downloading the image ('No image downloading required'), which gives clear context. However, it does not explicitly mention when not to use it or compare to alternatives, so it falls short of a 5.

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