Skip to main content
Glama

John's Essentials

by com.johnsessentials

photo_collage

Photo Collage — Arrange 2-16 images into a smart-cropped collage with aspect-ratio-aware layouts, named magazine templates, or legacy NxM grids. Output: JPG, PNG, WebP, AVIF. [category: photo]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gapNoGap between cells in px, 0-100.
filesYes2-16 images — JPG, PNG, WebP, HEIC. The multipart field name is 'files[]' (with brackets).
layoutNoLegacy NxM grid, e.g. 2x2, 3x3 (layout_mode=grid_legacy).
qualityNoOutput quality; 0 or omitted = engine default.
bg_colorNo'white', 'black', 'transparent', or hex (#abc/#aabbcc). Unknown values silently become white; jpg output flattens transparency to white.white
templateNoNamed template (layout_mode=template), e.g. ig_post_2x2, ig_story_3_vertical, magazine_5_hero.
layout_modeNoOmit to auto-infer: 'template' present implies template mode, 'layout' implies grid_legacy, otherwise smart.smart
aspect_ratioNoOutput aspect ratio (smart mode).
output_widthNoLegacy alias for output_long_edge.
output_formatNo'jpeg' is accepted as an alias for jpg. png ignores 'quality' (fixed compression).jpg
output_long_edgeNoOutput long edge in px.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already provide a non-read-only, non-destructive safety profile; the description adds the useful behavioral facts that 2-16 inputs are arranged and that output can be JPG/PNG/WebP/AVIF. It does not disclose side effects beyond that, but none are strongly implied.

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?

One dense introductory sentence followed by an output-format list and category tag. Every sentence contributes, and the 2-16 image scope and layout modes are front-loaded before the output detail.

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?

Given the very thorough input schema with 100% parameter coverage and enums, the brief description plus output formats is mostly sufficient. The main gap is the missing explicit relationship to sibling tools, but the schema and description together cover count, formats, layouts, and parameters.

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 parameters are already well documented. The description only summarizes layout modes and output formats at a high level and adds no new meaning that isn't in the schema.

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 action and resource: arrange 2-16 images into a collage, and enumerates layout modes and output formats. It is clear but does not explicitly differentiate from sibling photo_collage_animated or photo_collage_mosaic, so it falls short of full differentiation.

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 says what the tool can do (templates, grids, smart layout) but gives no guidance on when to choose this over photo_collage_animated or photo_collage_mosaic, and no exclusions or conditions. The alternative-selection burden is left entirely to the agent.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation2/5

Multiple tool pairs are near-identical: octopus_mkdir/octopus_make_folder and octopus_move/octopus_move_file are literal duplicates, analyze_hash/generate_hash both compute hashes, convert_word_to_pdf overlaps convert_document, and photo_compress/photo_compress_to_size plus pdf_thumbnails/pdf_to_images have fuzzy boundaries. The descriptions are detailed and cross-reference each other helpfully, but at 144 tools an agent will regularly misselect.

Naming Consistency3/5

The dominant {category}_{verb}_{object} snake_case pattern (pdf_*, photo_*, convert_*, analyze_*, media_*) is largely consistent and predictable. However, outliers like chatwithyourpdf and describe_image break the category-prefix convention, and the octopus namespace mixes bare verbs (read, write, mkdir) with verb_noun forms (make_folder, move_file, search_meta) inconsistently.

Tool Count2/5

144 tools is an extreme count for any MCP server. The broad scope (PDF, photo, video, audio, conversion, analysis, generation, file storage, web, e-sign) justifies some volume, but the count is inflated by batch and inspect variants (pdf_to_excel + batch + inspect), duplicate tools, and overlapping converters. An agent faces an overwhelming selection surface.

Completeness4/5

Per-domain coverage is remarkably deep: PDF spans merge/split/compress/protect/unlock/metadata/OCR/watermark and bidirectional conversion; photo covers editing, format conversion, face handling, OCR, and collage; file storage has full CRUD plus search. Minor gaps exist (no audio transcription, no video metadata editing, no deletion of PDF pages is actually covered via pdf_delete_pages) but the surface has no dead ends for its declared domains.

Resources