Skip to main content
Glama

John's Essentials

by com.johnsessentials
OverviewDiscussionsAdmin

photo_face_blur

Face Blur — Automatically detect and blur faces in a photo for privacy protection. [category: photo]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesJPG, PNG, WebP, BMP (max 25MB)
blur_modeNogaussian softens, pixelate mosaics, solid draws an opaque black box — solid is the only mode that survives deblurring attacks.gaussian
block_sizeNoSize of each mosaic square. 0 uses the amount chosen above; 1 is ignored, use 2 or more.
blur_radiusNoGaussian radius override. 0 = auto from blur_strength.
manual_facesNoAdvanced: extra rectangles to blur even if no face was found there, as [{"x":10,"y":20,"w":80,"h":80}] in pixels.
blur_strengthNoPreset intensity 1-4. blur_radius/block_size overrides beat it when set; irrelevant for solid mode.
output_formatNoOptional output format; defaults to the input format.
selected_facesNoAdvanced: which detected faces to blur, as a list of numbers starting at 0, e.g. [0,2]. Leave empty to blur every face found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / block_size / description
      Previous value: -"Pixelate block size override. 0 = auto from blur_strength."New value: +"Size of each mosaic square. 0 uses the amount chosen above; 1 is ignored, use 2 or more."
    • addedInput schema / properties / block_size / x-show-when
      Added value: +{
+  "blur_mode": [
+    "pixelate"
+  ]
+}
    • addedInput schema / properties / blur_radius / x-show-when
      Added value: +{
+  "blur_mode": [
+    "gaussian"
+  ]
+}
    • addedInput schema / properties / blur_strength / x-show-when
      Added value: +{
+  "blur_mode": [
+    "gaussian",
+    "pixelate"
+  ]
+}
    • changedInput schema / properties / manual_faces / description
      Previous value: -"Optional JSON array of manual face rectangles to blur."New value: +"Advanced: extra rectangles to blur even if no face was found there, as [{\"x\":10,\"y\":20,\"w\":80,\"h\":80}] in pixels."
    • addedInput schema / properties / output_format / enum
      Added value: +[
+  "jpg",
+  "png",
+  "webp",
+  "bmp"
+]
    • changedInput schema / properties / selected_faces / description
      Previous value: -"Optional JSON array of detected-face indexes to blur (default: all)."New value: +"Advanced: which detected faces to blur, as a list of numbers starting at 0, e.g. [0,2]. Leave empty to blur every face found."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnlyHint=false, destructiveHint=false, closed-world), so the bar is lower. The description adds only that detection is automatic; it says nothing about what is produced or whether the original is preserved, which is a meaningful gap for a mutation tool. However, the schema carries rich behavioral detail (e.g. that solid mode survives deblurring attacks).

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?

A single front-loaded sentence that states the action and the benefit with no wasted words. The '[category: photo]' tag is a minor routing aid but is slightly redundant metadata.

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?

With 8 parameters, no output schema, and no annotations describing output, the description should ideally state what the tool returns (a new blurred file vs. in-place mutation) and whether the original is retained. As written it leaves that to inference, though the schema fully covers the inputs.

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 both enums, defaults, ranges, and the blur_mode trade-offs are fully documented in the schema itself. The description adds no parameter meaning beyond the schema, making 3 the correct baseline.

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+resource ('detect and blur faces in a photo') plus a motive ('for privacy protection'), so the agent immediately knows what it does. It does not name any sibling (e.g. photo_face_detect, which detects but does not blur) to disambiguate, so it stops short of a 5.

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?

The phrase 'for privacy protection' implies the use case, but there is no explicit when-to-use, when-not-to-use, or alternative routing against siblings like photo_face_detect or photo_editor. Usage is only inferable.

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 toolsInspect
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