Skip to main content
Glama

image_exif

Extract EXIF metadata—camera model, timestamps, and GPS coordinates—from local images or image URLs to geolocate photos and verify whether metadata was stripped.

Instructions

Extract EXIF metadata (camera, timestamps, GPS) from a local image or image URL.

GPS coordinates are converted to decimal degrees when present. Useful for geolocating photos and checking whether metadata was stripped.

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": {
      "source": "<source>"
    },
    "name": "image_exif"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose one real behavioral detail beyond the obvious – GPS coordinates are normalized to decimal degrees – and confirms both local paths and URLs are accepted. It is silent on what happens when EXIF is absent, whether missing files error out, or whether the call is a pure read with no side effects.

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?

Two short sentences, front-loaded with the action and the extracted fields, followed by practical context. No filler, though the 'Useful for...' sentence is the weakest and borders on generic.

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 single-parameter read tool with no output schema, the description covers input forms, the categories of returned metadata, and one normalization rule. The remaining gap is failure/empty-result behavior, which is minor relative to the tool's simplicity.

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 0% and the single parameter is blandly named 'source', but the description clarifies it accepts either a local image path or an image URL. That is exactly the kind of meaning the schema fails to convey, so the description meaningfully compensates for the coverage gap.

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: extract EXIF metadata (camera, timestamps, GPS) from a local image or image URL. An agent immediately knows what comes back and what inputs are accepted. It does not explicitly distinguish itself from nearby siblings such as image_analyze, so it falls short of a 5.

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?

The line 'Useful for geolocating photos and checking whether metadata was stripped' gives implied scenarios for use, which is more than nothing. However, it offers no explicit when-not guidance and never names an alternative tool for, say, visual content analysis versus metadata inspection.

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