Skip to main content
Glama

Обрезать фото

crop_image

Обрезает фото по рамке, формат сохраняется. file_url: публичный URL фото. box: [x0, y0, x1, y1] долями кадра (0–1, от левого верхнего угла; фото повёрнуто по EXIF).

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": {
      "file_url": "<file_url>",
      "box": "<box>"
    },
    "name": "crop_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYes
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds genuinely useful behavior beyond that: the output format is preserved and the coordinate space accounts for EXIF rotation, which materially affects how a caller computes the box. It does not say whether the source is replaced or a new asset is produced, but the openWorldHint and existing output schema reduce that gap.

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?

One sentence of purpose followed by two compact parameter lines, with the behavioral caveat (format preserved) front-loaded. No filler, and each clause carries information an agent needs to call the tool correctly.

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 two-parameter tool with an output schema, the description covers purpose, both parameters, and the EXIF/format behaviors. Minor gaps remain — no mention of whether a new file or URL is returned in the response body and no size or URL-access constraints — but these are modest given the output schema.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does it well: file_url is defined as a public photo URL, and box is defined as [x0, y0, x1, y1] in normalized 0–1 fractions measured from the top-left, with EXIF rotation noted. This is exactly the semantics the bare array-of-numbers schema cannot 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?

The description states a specific verb and resource ('Обрезает фото по рамке') plus a scope note that the format is preserved. The photo-vs-PDF distinction from the sibling crop_pdf is implied by the word 'фото', but the sibling is never 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?

Usage is only implied: an agent can infer this is the tool for cropping raster images, but the description gives no when-to-use conditions, no prerequisites (e.g. public URL must be reachable), and no pointer to crop_pdf or rotate_image for adjacent cases.

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.