Skip to main content
Glama
Foto MCP Server
by thesven

foto_parse_xmp

Parse Adobe Lightroom, Capture One, or Darktable .xmp sidecar files to extract star ratings, color labels, keywords, copyright, lens, and Fuji film simulation data.

Instructions

Parse an Adobe Lightroom, Capture One, or Darktable .xmp sidecar file (or find the sidecar for an image file). Extracts star ratings (xmp:Rating), color labels (xmp:Label), title, description, hierarchical keywords, copyright, lens, and Fuji film simulation recipes.

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": {
      "filePath": "<filePath>"
    },
    "name": "foto_parse_xmp"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute path to the .xmp sidecar file or its parent image file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does well by enumerating what is extracted (xmp:Rating, xmp:Label, title, description, keywords, copyright, lens, Fuji recipes), which is real return-value information, but it never states what happens when no sidecar exists, whether the call is purely read-only, or how errors are surfaced.

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 tightly packed sentences with the core action front-loaded and the extracted-field list following as supporting detail. No filler, no repetition, and the dual-input behavior arrives before the payoff list.

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-style tool with no output schema, listing the extracted fields is the right compensation, and the description does that. The remaining gap is failure behavior when a sidecar is missing or unreadable, which an agent would need before calling confidently.

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?

Schema description coverage is 100% and the schema already explains that filePath accepts an absolute path to a sidecar or its parent image. The description's opening clause restates this rather than adding new meaning, so it sits at the baseline rather than above it.

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 (parse) and resource (.xmp sidecar) and even covers the dual mode of accepting either a sidecar or its parent image file. It is clear enough that an agent can select it without opening the schema, though it never names or contrasts a sibling such as foto_inspect_image, which plausibly overlaps on 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 Guidelines3/5

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

Usage is only implied: the phrase 'or find the sidecar for an image file' tells the agent what inputs are acceptable, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the calling context from the tool's purpose alone.

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