Skip to main content
Glama

binary-forensics

exif_inspect_and_strip

Inspect JPEG APP1 EXIF/XMP/ICC segments for GPS coordinates, camera Make/Model, and timestamps, and optionally strip metadata cleanly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exif_inspect_and_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo
outputPathNo
stripMetadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and falls short. It does not say that stripping is irreversible/destructive, whether stripping rewrites the source file in place or writes elsewhere, what permissions are needed, or whether the JPEG-only constraint means other formats error out. The word 'cleanly' gestures at quality but conveys nothing verifiable.

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?

One front-loaded sentence that names the format, the segments, the extracted fields, and the optional destructive mode, with no filler. It is compact, though the two-in-one inspect/strip framing is slightly harder to parse than a single-purpose statement would be.

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

Completeness2/5

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

Given no annotations, no output schema, four undocumented parameters, and a potentially destructive operation, the description is materially incomplete. An agent cannot determine where output is written, how inputs are mutually exclusive, or what the return value looks like before committing to a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for four parameters, so the description must compensate and largely does not. Only stripMetadata is indirectly explained ('optionally strip metadata'), while filePath, base64Data, and outputPath are never mentioned — leaving the agent to guess whether the data can come from a path or inline base64, and where stripped output goes.

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?

The description gives a specific verb and resource — 'Inspect JPEG APP1 EXIF/XMP/ICC segments' — plus the concrete data targets (GPS, Make/Model, timestamps). It also flags a second mode ('optionally strip metadata'), which separates it from siblings like hexdump_inspect or executable_inspect that inspect other formats, though the dual inspect/strip purpose blurs the single-tool identity slightly.

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

Usage Guidelines2/5

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

There is no when-to-use vs when-not guidance. It never says when stripping is appropriate versus inspection-only, never clarifies which sibling to use for non-JPEG metadata, and gives no guidance on the alternative input sources (filePath vs base64Data) or when outputPath is needed.

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