Skip to main content
Glama

case_image_crop

Crop a specific pixel region from a case image for closer visual inspection and save the result as a new case image.

Instructions

Crop a region for closer visual inspection and save it as a new case image.

Coordinates are pixels from the top-left. An optional person label only files the crop in that person's folder; it does not verify identity.

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": {
      "case": "<case>",
      "image_id": "<image_id>",
      "left": "<left>",
      "top": "<top>",
      "right": "<right>",
      "bottom": "<bottom>"
    },
    "name": "case_image_crop"
  }
}

Input Schema

NameRequiredDescriptionDefault
topYes
caseYes
leftYes
rightYes
bottomYes
personNo
image_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden, and it does disclose a key behavior: the operation creates and saves a new image rather than returning a transient result, and the person label is purely organizational and does not verify identity. It omits whether the crop can be re-cropped, how out-of-bounds coordinates are handled, and what the caller receives back.

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?

Three short sentences, front-loaded with the action, then coordinate semantics, then the caveat about the person label. Nothing is redundant and every sentence carries information.

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 7-parameter mutation with no annotations and no output schema, the description covers the tricky inputs well but leaves the result of the call undefined—there is no indication of what identifier or path the new image gets, which the agent may need for follow-up steps. It is adequate but not complete.

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 0%, so the description has to compensate, and it does so for the most error-prone inputs: the four coordinate parameters are defined as pixels measured from the top-left, and the optional person parameter is clarified as filing-only. The case and image_id parameters get no format or origin details, which is the remaining gap.

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 states a specific verb and resource: crop a pixel region and persist it as a new case image. That is clearly distinguishable from sibling read tools like case_image_view or case_image_similar, though no sibling is named explicitly.

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?

The phrase 'for closer visual inspection' implies the use case, so an agent can infer it is for zooming into a detail worth examining. However, it gives no when-not guidance, no prerequisites such as needing an existing image_id, and no alternatives.

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