Skip to main content
Glama

Повернуть фото

rotate_image

Поворачивает и отражает фото, формат сохраняется. Одно фото — файл, несколько — ZIP. file_urls: публичные URL фото. angle: 0 | 90 (по умолчанию) | 180 | 270 — по часовой. flip: horizontal | vertical — отражение после поворота.

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_urls": "<file_urls>"
    },
    "name": "rotate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNo
angleNo
file_urlsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (non-destructive, non-idempotent, open-world), and the description adds real value on top: the output format is preserved, one image returns a file, several return a ZIP, and the inputs must be public URLs. It does not state whether originals are left untouched or what happens on an unsupported format, but the artifact-shape disclosure is the most useful thing it could add.

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?

Two sentences of behavior followed by one line per parameter — front-loaded, scannable, and free of filler. Every clause carries information the agent could not get from the schema.

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 an output schema present, return values need not be explained, yet the description still flags the single-file vs ZIP artifact difference, which matters for downstream handling. Combined with the parameter semantics and the public-URL precondition, nothing an agent needs in order to call this correctly is missing.

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 coverage is 0% and the schema gives the agent nothing: angle is a bare integer with a default and flip is an unconstrained anyOf string/null. The description compensates fully by enumerating the allowed angles (0/90/180/270, 90 default, clockwise) and the flip values (horizontal|vertical, applied after rotation), plus the meaning of file_urls as public URLs.

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?

"Поворачивает и отражает фото, формат сохраняется" gives a concrete verb pair plus the resource (photos), which implicitly separates it from the sibling rotate_pdf and from crop_image/resize_image. It stops short of naming an alternative explicitly, so routing is inferred from the resource word rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no mention of the closely related rotate_pdf sibling. The description only states what the tool does mechanically, leaving the agent to infer that PDFs belong to rotate_pdf and that cropping/resizing are different tools.

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.