Skip to main content
Glama
Sign In
Media Toolkit MCP Server

Media Toolkit MCP Server

by kevinten-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_collage

Create a grid collage from multiple images. Resizes each image to fit uniformly in the grid.

Instructions

Arrange multiple images into a grid collage. Images are resized to fit uniformly. Works locally with Pillow.

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": {
      "image_paths": "<image_paths>"
    },
    "name": "create_collage"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnsNoNumber of columns in the grid (default: 2)
spacingNoSpacing between images in pixels (default: 10)
image_pathsYesList of image file paths to include in the collage
output_pathNoPath to save the output collage (optional, auto-generated if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so the description must carry full burden. It only states 'Images are resized to fit uniformly' and 'Works locally with Pillow', lacking details on side effects, error handling, or permission requirements.

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?

Two concise sentences front-loading the main action with no wasted 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?

Given no output schema and simple tool, description covers basic operation but omits output format details, error conditions, and prerequisites (e.g., image existence). Adequate but with gaps.

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 baseline is 3. The description adds no extra meaning to individual parameters beyond what the schema provides.

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?

Clearly states the verb 'Arrange' and resource 'multiple images into a grid collage', and distinguishes from sibling tools like convert_format, remove_background, etc. by specifying the collage goal.

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 explicit guidance on when to use this tool vs alternatives. The description implies use for collage creation but lacks exclusions or context about prerequisites.

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