Skip to main content
Glama
Sign In
rawtherapee-mcp-server

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_exif

Extract camera settings from RAW images, such as ISO and aperture, to improve processing decisions on noise reduction and white balance.

Instructions

Read EXIF metadata from a RAW image file.

Returns camera settings (ISO, aperture, shutter speed, focal length, etc.) used when the photo was taken. Use this to make better decisions about processing parameters like noise reduction, lens correction, and white balance. Params: file_path

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": {
      "file_path": "<file_path>"
    },
    "name": "read_exif"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It accurately describes a read operation with no side effects, but lacks details on error handling, file compatibility beyond RAW, or performance considerations.

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 sentences plus a parameter note. Purpose is front-loaded, and the second sentence adds value. The 'Params:' line is slightly redundant but not harmful. Overall efficient.

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

Completeness3/5

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

Output schema exists, so return details are less critical. Description lists sample returned fields, which is good. Missing details: error handling, file existence checks, or whether non-RAW files are rejected. Could be more thorough for a tool with no annotations.

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 has one parameter (file_path) with no description. The description adds 'Params: file_path' but does not explain its format, constraints, or behavior (e.g., absolute vs relative path). For a single obvious parameter, this is baseline value.

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?

Clearly states the action (read EXIF metadata), the resource (RAW image file), and lists specific metadata fields (ISO, aperture, etc.). Distinguishes from siblings like inspect_metadata and get_image_info by targeting EXIF specifically from RAW files.

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?

Provides a clear use case: informs processing decisions like noise reduction and lens correction. However, it does not explicitly compare to alternatives or state when not to use it, missing some usage guidance.

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