Skip to main content
Glama
Sign In
stayput-mcp

stayput-mcp

by keenanlk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect photo metadata

inspect_image_metadata
Read-only

Report hidden metadata in JPG, PNG, WebP, or HEIC photos—GPS, camera, capture time, software, and EXIF/XMP/IPTC blocks—so you can review what to remove. Read-only.

Instructions

Report the metadata hidden in a JPG, PNG or WebP photo: GPS location, camera make and model, capture time, editing software, and which blocks (EXIF, XMP, IPTC, comments) are present. HEIC files report EXIF only. Read-only: nothing is written. Use before strip_image_metadata to see what would be removed.

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": {
      "path": "<path>"
    },
    "name": "inspect_image_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description's 'Read-only: nothing is written' is largely redundant. However, it adds genuine behavioral context beyond the annotations: format-specific degradation (HEIC reports EXIF only) and the set of metadata blocks it surfaces.

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?

Three tight sentences, front-loaded with what is reported, then format edge case, then read-only guarantee and routing advice. No filler or repetition.

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?

No output schema exists, so the description compensates by enumerating the returned fields and block types. Combined with the explicit read-only statement and the sibling routing note, an agent has everything needed to select and call 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?

A single required 'path' parameter at 100% schema description coverage, so the schema already documents the input fully. The description adds no syntax, format, or constraint detail about the path (e.g., relative vs absolute, remote URLs), which matches the baseline 3 when the schema does the heavy lifting.

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?

States a specific verb ('Report') and resource (photo metadata) and enumerates exactly what is reported: GPS, camera make/model, capture time, editing software, and present blocks. It also scopes supported formats (JPG/PNG/WebP, with HEIC limited to EXIF), which cleanly separates it from the write-side sibling strip_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 Guidelines5/5

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

Explicitly names the alternative workflow: 'Use before strip_image_metadata to see what would be removed.' The condition that selects this tool over its sibling is stated outright rather than left to inference.

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