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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_lens_support

Check if a camera-lens combination has a Lensfun calibration profile via EXIF from RAW files or manual camera/lens parameters.

Instructions

Check whether a camera/lens combination has a Lensfun calibration profile.

Reads EXIF from a RAW file to detect camera/lens automatically, or accepts manual camera_make, camera_model, lens_model parameters. Parses the local Lensfun XML database (configured via RT_LENSFUN_DIR or auto-detected). Params: file_path (optional RAW for EXIF detection), camera_make, camera_model, lens_model

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

Input Schema

NameRequiredDescriptionDefault
file_pathNo
camera_makeNo
camera_modelNo
lens_modelNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.2/5.0
Behavior3/5

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

Describes reading EXIF and parsing XML database, but lacks details on side effects, authorization needs, or error conditions. No annotations to supplement.

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?

Concise, front-loaded with main purpose, every sentence adds value. No redundant information.

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?

Covers core behavior and parameters adequately; return value not detailed (output schema exists). Could mention output format but not essential.

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

Parameters4/5

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

Schema has 0% description coverage; description lists all parameters and briefly explains each, adding meaning beyond the bare schema.

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 tool checks if a camera/lens combination has a Lensfun calibration profile. Uses specific verb and resource, and contrasts with sibling tools like apply_lens_correction.

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?

Explains two modes of use (auto-detection via file_path or manual params). Does not explicitly state when not to use, but contextually clear.

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