Skip to main content
Glama

cutout

Trim transparent edges, crop a percentage off any side, or flip a picture in a shot. Returns the new size and keeps one undo step.

Instructions

Free picture fixes on this computer for a picture already in a shot: trim its empty see-through edges, crop a percent off each side, or flip it. Give member (a cast member id with a picture) or leave it out for the shot's background picture. One undo step. Returns the new size. To remove a background (paid), use remove_background.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cutout"
  }
}

Input Schema

NameRequiredDescriptionDefault
cropNoPercent (0-45) off each side.
flipNotrue: mirror it left to right.
shotNoShot id (from get_project). Default: the shot on screen.
trimNotrue: cut empty see-through edges.
memberNoA cast member id with a picture. Left out: the shot's background picture.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.2
    • addedInput schema / properties / crop / properties / bottom / description
      Added value: +"Percent off the bottom."
    • addedInput schema / properties / crop / properties / left / description
      Added value: +"Percent off the left."
    • addedInput schema / properties / crop / properties / right / description
      Added value: +"Percent off the right."
    • addedInput schema / properties / crop / properties / top / description
      Added value: +"Percent off the top."
    • addedInput schema / properties / flip / description
      Added value: +"true: mirror it left to right."
    • addedInput schema / properties / member / description
      Added value: +"A cast member id with a picture. Left out: the shot's background picture."
    • addedInput schema / properties / trim / description
      Added value: +"true: cut empty see-through edges."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it is free, it operates on a local picture, changes cost 'One undo step' (a real cost/irreversibility signal that tempers destructiveHint=false), and it returns the new size. The paid counterpart is flagged so the agent does not accidentally route an unpaid request to remove_background.

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-loads the operation and target, then handles the target default, the undo cost, the return value, and the paid alternative in four tight sentences. No filler or repetition of schema structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return value ('the new size'); with destructiveHint=false on a pixel-removing tool, it supplies the undo cost; with 5 optional params, it clarifies the target default. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the schema already defines crop per-side percents, flip, trim, shot, and member including the 'left out = background picture' default. The description restates the member default but adds no range, format, or interaction detail (e.g., whether trim and crop can combine), so baseline 3 applies.

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 set (trim / crop / flip) applied to a specific resource (a picture already in a shot) and explicitly names the sibling it is not (remove_background). An agent can distinguish it from remove_background and the generate_* tools without opening the schema.

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

Usage Guidelines5/5

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

Gives the condition for use (fixing an existing picture: transparent-edge trim, percent crop, mirror), the condition for the alternative ('To remove a background (paid), use remove_background'), and the free-vs-paid distinction that forces the routing decision. Also states the default target when member is omitted.

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