Skip to main content
Glama

crop

Frames a chosen rectangle of the ASCII canvas as the new canvas and blanks cells outside the current grid, letting you isolate details or fix oversized renders.

Instructions

Crop the canvas to a rectangle; the cut-out becomes the new canvas. Cells outside the current grid become blank. Use it to frame a detail, cut a subject out of a larger render, or fix an oversized canvas.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "crop"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesLeft edge of the crop (canvas column).
yYesTop edge of the crop (canvas row).
widthYesCrop width in cells.
heightYesCrop height in cells.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the important consequence that the cropped rectangle replaces the canvas and that cells outside the current grid become blank. It does not say whether discarded content is recoverable or whether the canvas dimensions change persistently, which are relevant for a mutation operation.

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?

Two short sentences front-load the core behavior before a use-case sentence, and every clause carries information. Slightly more could be trimmed from the use-case list, but nothing is wasted.

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 four-required-parameter, no-annotation, no-output-schema tool, the definition covers what the tool does, the resulting canvas state, and typical applications. The main remaining gap is guidance on how this differs from adjacent canvas-shaping tools like trim or resize_canvas.

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%, and the schema already explains x/y as canvas column/row edges and width/height in cells with bounds. The description adds only the framing notion of a "rectangle" and does not extend meaning beyond the schema, so the baseline of 3 applies.

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?

The description names a specific verb and resource ("Crop the canvas to a rectangle") and states the resulting state ("the cut-out becomes the new canvas"), so the operation is unambiguous. It does not, however, distinguish itself from similar siblings such as trim or resize_canvas, leaving the agent to infer the difference.

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?

It gives three concrete situations to use the tool: framing a detail, cutting a subject out of a larger render, and fixing an oversized canvas. That is clear positive guidance, but no when-not-to-use condition and no named alternative (e.g., trim vs. resize_canvas) is offered.

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