Skip to main content
Glama

Read camera, date and GPS metadata from an image

exif
Read-only

Camera make and model, lens, date taken, exposure (ISO, shutter, aperture, focal length), orientation, image size, software, and GPS latitude, longitude and altitude with a map link, from the EXIF of a JPEG, HEIC, TIFF or PNG image at a URL. Only the first 256 KB is read. A file that is not an image is 415; an image without EXIF is 200 with hasExif false. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL of a JPEG, HEIC, TIFF or PNG image

Output Schema

NameRequiredDescriptionDefault
gpsNo
urlNo
noteNo
widthNo
cameraNo
formatNo
hasGpsNo
heightNo
hasExifNo
takenAtNo
exposureNo
finalUrlNo
bytesReadNo
checkedAtNo
orientationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bytesRead": {},
      +    "camera": {},
      +    "checkedAt": {},
      +    "exposure": {},
      +    "finalUrl": {},
      +    "format": {},
      +    "gps": {},
      +    "hasExif": {},
      +    "hasGps": {},
      +    "height": {},
      +    "note": {},
      +    "orientation": {},
      +    "takenAt": {},
      +    "url": {},
      +    "width": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses non-obvious operational traits: only the first 256 KB is read, non-image input yields 415, an EXIF-less image yields 200 with hasExif false, and the call costs $0.002 via x402 with failed calls uncharged. Cost and partial-read behavior are exactly the kind of context an agent cannot infer from structured fields.

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?

Two sentences, both front-loaded: the returned fields come first, then limits, error semantics, and pricing. The field enumeration is long but every item is meaningful payload information, and there is no filler or hedging.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with an output schema already covering return shape, the description supplies everything else an agent needs: input formats, size cap, failure modes, and billing. Nothing material is left implicit.

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?

With a single parameter at 100% schema coverage, the schema already defines the url field and its accepted image types. The description restates the supported formats and https requirement rather than adding new syntax or constraints, so the baseline of 3 applies.

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 opens with a concrete inventory of the resource returned — camera make/model, lens, date taken, exposure, orientation, GPS with map link — and names the exact source formats and input form (URL). A specific verb-plus-resource statement like this lets an agent distinguish it from generic image or file readers without consulting the schema.

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?

Usage context is clear: it is for pulling EXIF out of an image reachable by URL, and the stated 415/200-with-hasExif-false outcomes tell the agent what to expect when the target is not an image or lacks metadata. It stops short of naming an explicit alternative or exclusion (e.g., when to prefer a general image-description tool), so it lands just below the top band.

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