Skip to main content
Glama

Set crop

snipaya_set_crop

Crops image exports to a defined rectangle, or removes the crop when given null.

Instructions

Crop exports to a rectangle, or pass null to remove the crop.

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": {
      "rect": "<rect>"
    },
    "name": "snipaya_set_crop"
  }
}

Input Schema

NameRequiredDescriptionDefault
rectYes
tabIdNoTarget tab id. Defaults to the active tab.
relativeToNoImage id from snipaya_get_canvas. When set, all coordinates in this call are pixels of that image as captured (the same pixels you see in snipaya_render of that image).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is covered. The description adds real value by disclosing that the crop affects exports and is reversible via null, but says nothing about persistence (save_project) or whether it affects render vs export only.

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?

A single sentence that front-loads the action and pairs it with the reset path. Nothing redundant.

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?

For a 3-parameter mutation with no output schema, the description covers the core effect and the reset path but omits whether the crop persists to the saved project and how it interacts with per-tab scope or export destinations.

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 67%, with rect/tabId/relativeTo each described. The description's key contribution is explaining what null means semantically—remove the crop—which the schema's bare 'anyOf null' does not convey.

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?

A specific verb+resource: it sets the crop rectangle applied to exports. It clearly implies a state mutation on the canvas, though it never names the sibling tools it relates to (render, export) to sharpen the mental model.

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

Usage Guidelines3/5

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

It tells you how to remove a crop (pass null) but not when to use this tool versus manipulating a canvas via snipaya_get_canvas or checking the result via snipaya_render. Usage is implied rather than guided.

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