John's Essentials

photo_noise_reducer

Noise Reducer — Reduce image noise and grain using ImageMagick's denoising filters. [category: photo]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file`	Yes	JPG, PNG, WebP, BMP, TIFF (max 25MB)
`mode`	No	Denoise algorithm.	auto
`sharpen`	No	Optional post-denoise sharpening.	none
`strength`	No	STRING enum '1'-'4', not an int. Invalid values silently become '2'. Ignored when mode=smart — the analyzer overrides it.	2
`output_format`	No	Optional output format; defaults to the input format.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026
- addedInput schema / properties / output_format / x-ui
```
Added value: +{
+  "unset_label": "Keeps input format"
+}
```

Changed4 schema fields changedSep 11, 2026

addedInput schema / properties / mode / x-ui

Added value: +{
+  "labels": {
+    "auto": "Balanced",
+    "dctdnoiz": "Best for JPEG blockiness (slow)",
+    "despeckle": "Gentle speckle removal",
+    "gaussian": "Soft blur",
+    "luminance": "Keep colour, smooth brightness",
+    "median": "Speckle removal",
+    "nlmeans": "Best quality (slow)",
+    "smart": "Let the tool decide"
+  }
+}

addedInput schema / properties / sharpen / x-show-when

Added value: +{
+  "mode": [
+    "auto",
+    "median",
+    "despeckle",
+    "gaussian",
+    "luminance",
+    "nlmeans",
+    "dctdnoiz"
+  ]
+}

addedInput schema / properties / strength / x-show-when

Added value: +{
+  "mode": [
+    "auto",
+    "median",
+    "despeckle",
+    "gaussian",
+    "luminance",
+    "nlmeans",
+    "dctdnoiz"
+  ]
+}

addedInput schema / properties / strength / x-ui

Added value: +{
+  "labels": {
+    "1": "Light",
+    "2": "Medium",
+    "3": "Strong",
+    "4": "Maximum"
+  }
+}

First observedSep 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The annotations already convey that the tool is not read-only and not destructive, so the bar is lowered. The description adds a small amount of implementation context ('using ImageMagick's denoising filters') but does not disclose output behavior, whether the input file is modified, or what the response contains. This is acceptable but not rich.

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?

The description is compact and front-loaded, with no unnecessary sentences. The opening 'Noise Reducer —' is somewhat redundant with the tool name/title, and '[category: photo]' is a mild tag, but overall the description stays concise and scannable.

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

Completeness2/5

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

With no output schema, the description does not explain what the tool returns (e.g., a file path, URL, or image data). It also omits any usage context or behavior beyond the core operation. The rich input schema compensates for parameter understanding, but the definition is incomplete for an agent trying to predict the tool's full behavior.

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%, so the baseline is 3. The description itself adds no parameter-specific meaning; the schema already provides useful details like enum choices, defaults, x-ui labels, and the note that invalid strength values silently become '2'.

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 clearly states the specific action ('Reduce image noise and grain') and identifies the underlying tooling (ImageMagick's denoising filters). It is not a tautology and is distinguishable from the sibling photo tools by its function, though it does not explicitly call out any sibling alternatives.

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?

The description gives no guidance on when to use this tool versus alternatives such as photo_editor or photo_color_adjuster. There is no mention of ideal use cases, prerequisites, or exclusions, so the agent must infer usage entirely from the tool name and brief purpose.

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

All John's Essentials tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?