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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_histogram

Analyze tonal distribution of a JPEG, TIFF, or PNG image by computing RGB histograms and statistics (mean, median, std_dev, min, max) with clipping percentages. Optionally includes an SVG visualization.

Instructions

Compute RGB histogram and image statistics for a processed image.

Analyzes the tonal distribution of a JPEG, TIFF, or PNG image. Returns per-channel histograms (256 bins), statistics (mean, median, std_dev, min, max), and clipping percentages. Optionally includes an SVG visualization. Params: file_path, include_svg

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

Input Schema

NameRequiredDescriptionDefault
file_pathYes
include_svgNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.5/5.0
Behavior4/5

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

Discloses that it computes histograms, statistics, and clipping percentages, and optionally includes an SVG. It is read-only and does not modify data. Without annotations, this adds value.

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?

Concise and front-loaded with the main purpose. The 'Params' line is slightly redundant but not harmful. No unnecessary words.

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?

Covers the main outputs and file types. With an output schema present, it is fairly complete but lacks details on file_path requirements and edge cases.

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?

Only lists parameter names ('file_path, include_svg') without explaining expected formats, values, or behavior. Schema coverage is 0%, so description does not compensate.

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?

The description clearly states it computes RGB histograms and image statistics for processed images of specific formats. It also lists the returned data, making the purpose unmistakable.

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?

No guidance on when to use this tool versus sibling analysis tools like 'analyze_image' or 'get_image_info'. It implies tonal analysis but lacks explicit usage context or exclusions.

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