Skip to main content
Glama

Lay out Playground media for comparison

playground_media_compare
Idempotent

Compare 2–4 images or 2–4 videos side by side on the canvas. Two images fill a Compare (image-compare) node's A/B slots; three or four images feed a Picks (output-gallery) node; videos are grouped in one titled row. Inputs stay where they are except videos, which move into the new group. Free; revision checked and idempotent. It does not judge quality. Returns comparison layout, selected node IDs, summaries, revision and Playground URL.

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": {
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>",
      "nodeIds": "<nodeIds>"
    },
    "name": "playground_media_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoHuman-readable label to display for this item in Playground.
nodeIdsYesIDs of the existing canvas nodes to use for this action.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
layoutYes
nodeIdsYes
summaryYes
replayedYes
revisionYes
canvasUrlYes
compareNodeIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false; the description adds real value on top by disclosing mutation scope ('Inputs stay where they are except videos, which move into the new group'), cost ('Free'), and revision-conflict handling. It does not spell out what happens on partial failure or what a conflict response looks like, but the key side effect is disclosed.

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?

Front-loaded with the action and cardinality, then branching behavior, side effects, cost/revision semantics, and a scope exclusion — no filler sentences. Every clause carries information an agent needs before calling.

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?

For a mutating, revision-guarded tool with a full output schema, the description covers action, branching, side effects and cost. Remaining gaps are minor: the optional 'title' parameter's role and expected error/conflict behavior are left entirely to the schema rather than being reinforced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by explaining that the nodeIds count changes the resulting node type (2 vs 3–4) and that video inputs are regrouped. That is genuine semantic meaning not present in the schema's generic 'IDs of the existing canvas nodes' wording.

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?

States a specific verb and resource ('Compare 2–4 images or 2–4 videos side by side on the canvas') with cardinality bounds and names the concrete node types produced (image-compare A/B slots, output-gallery Picks, titled video row). This is clearly distinguishable from siblings like playground_media_compose and playground_canvas_arrange without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear selection logic driven by input count and media type (2 images -> Compare node, 3–4 images -> Picks node, videos -> one titled row), and explicitly excludes a quality-judgment use case. It stops short of naming an alternative tool for cases this one doesn't fit (e.g., arranging non-media nodes), so guidance is strong but not fully comparative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.