John's Essentials

photo_image_splitter

Image Splitter — Split an image into a grid of equal tiles (e.g. 2x2, 3x3). [category: photo]

Input Schema

TableJSON Schema

Name	Required	Description
`cols`	No	Columns, 1-8. The rightmost column absorbs remainder px, so tile widths can differ slightly.
`file`	Yes	Image to split — JPG, PNG, WebP, or BMP (max 30 MB). Output is ALWAYS a ZIP of tiles, even for tiny grids.
`rows`	No	Rows, 1-8. The bottom row absorbs remainder px. rows x cols tiles come back in one ZIP.
`output_format`	No	Optional tile format; defaults to the input format.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

addedInput schema / properties / cols / x-ui / draw

Added value: +{
+  "of": "grid",
+  "role": "cols"
+}

addedInput schema / properties / rows / x-ui

Added value: +{
+  "draw": {
+    "of": "grid",
+    "role": "rows"
+  }
+}

addedInput schema / x-draw

Added value: +{
+  "grid": {
+    "noun": "grid",
+    "shape": "grid",
+    "title": "Where it is cut"
+  }
+}

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / cols / x-ui
```
Added value: +{
+  "pair_label": "Grid",
+  "pair_with": "rows"
+}
```
Changed3 schema fields changedSep 24, 2026
- addedInput schema / properties / cols / title
```
Added value: +"Columns"
```
- removedInput schema / properties / cols / x-ui
```
Removed value: -{
-  "unit": "columns"
-}
```
- removedInput schema / properties / rows / x-ui
```
Removed value: -{
-  "unit": "rows"
-}
```
Changed1 schema field changedSep 24, 2026
- addedInput schema / properties / output_format / x-ui
```
Added value: +{
+  "unset_label": "Keeps input format"
+}
```
Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / cols / x-ui
```
Added value: +{
+  "unit": "columns"
+}
```
- addedInput schema / properties / rows / x-ui
```
Added value: +{
+  "unit": "rows"
+}
```
Changed1 schema field changedSep 11, 2026
- addedInput schema / properties / output_format / enum
```
Added value: +[
+  "jpg",
+  "png",
+  "webp",
+  "bmp"
+]
```
First observedSep 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no further behavioral context such as output being a ZIP, permission needs, or what happens to the input — and that ZIP detail lives only in the schema. Nothing is contradicted, but the description contributes essentially no behavioral 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?

A single front-loaded sentence that states the operation and an example, with no padding. The trailing '[category: photo]' tag is minor overhead but doesn't obscure the core message.

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 one required 'file' parameter, four well-documented properties and no output schema, the description is minimally sufficient to call the tool. It does not mention the ZIP return container or any failure modes, leaving the agent to rely entirely on schema text for those details.

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%, with cols, rows, file and output_format each fully documented in the schema (grid bounds, remainder-pixel behavior, ZIP output). The '2x2, 3x3' example is the only added hint, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Split an image') and pins down the operation as a 'grid of equal tiles', which naturally separates it from photo_crop or pdf_split. It stops short of naming or contrasting any sibling tool, so it lands at 4 rather than 5.

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 offers only the parenthetical example 'e.g. 2x2, 3x3', which is parameter illustration, not usage guidance. There is no statement of when to choose this over photo_crop, photo_resize, or the many other photo_* siblings, and no preconditions or exclusions.

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?