AIGE

Move or remove a sticker

antix_place_deck_sticker

DestructiveIdempotent

Use this when the user asks 'make the sticker smaller', 'move it to the top right', 'tilt it a little' or 'remove the sticker'. Move, scale or turn one sticker on one slide, or take it off with remove. x and y are its centre as shares of the slide (0.5, 0.5 is the middle), width a share of the slide's width, rotation degrees clockwise; only what you pass changes, and it keeps its proportions. Read the sticker's id and place from the slide's stickers in the deck result. Require the current expectedVersion; on DECK_CONFLICT, read the deck again and repeat the same intended change. Free.

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": {
      "deckId": "<deckId>",
      "expectedVersion": "<expectedVersion>",
      "slideId": "<slideId>",
      "stickerId": "<stickerId>"
    },
    "name": "antix_place_deck_sticker"
  }
}

Input Schema

Name	Required	Description
`x`	No	Its centre across the slide: 0 left edge, 0.5 middle, 1 right edge.
`y`	No	Its centre down the slide: 0 top, 0.5 middle, 1 bottom.
`width`	No	Its width as a share of the slide's width (0.3 is about a third). Its height follows its own proportions.
`deckId`	Yes
`locale`	No
`remove`	No	true takes the sticker off the slide.
`slideId`	Yes
`rotation`	No	Its turn in degrees, clockwise.
`projectId`	No	AIGE project whose Canvas should receive the updated deck.
`stickerId`	Yes	The sticker's id, from the slide's stickers in the deck result.
`accountHandle`	No
`expectedVersion`	Yes	REQUIRED: the deck version you last read. A stale value fails with DECK_CONFLICT before any work.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the destructiveHint/idempotentHint annotations, it discloses the partial-update rule ('only what you pass changes'), aspect-ratio preservation, the required expectedVersion, the DECK_CONFLICT recovery loop and that the call is free. It does not say what happens to other stickers or whether a removal is recoverable, but the mutation semantics are unusually well covered here.

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?

The trigger examples are front-loaded, then the geometric semantics, then the versioning rule – a logical order with no filler. The single dense paragraph packs several distinct ideas together, which slightly hurts scannability.

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 12-parameter destructive mutation with no output schema, the description covers the critical call-correctness concerns: locating the sticker, supplying the version, and recovering from conflicts. The remaining gap is the meaning of the auxiliary identifiers (projectId, accountHandle, locale) and what the response returns.

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?

It adds genuine meaning for the geometry parameters (centre as shares of the slide, width as a share, degrees clockwise, proportional height) and the merge behavior. However, with only 67% schema description coverage, the four fully undocumented parameters (deckId, slideId, locale, accountHandle) are left unexplained in both places, including the non-obvious projectId routing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states specific verbs plus a bounded resource: 'Move, scale or turn one sticker on one slide, or take it off with remove.' The 'one sticker on one slide' scoping distinguishes it from deck-level siblings like antix_apply_deck_layout or antix_edit_deck_slides, and from antix_add_deck_sticker.

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 literal user phrasings that should trigger the tool ('make the sticker smaller', 'tilt it a little', 'remove the sticker') and points to the deck result as the source of the sticker id. It never names a sibling alternative, so an agent must infer that adding stickers belongs to antix_add_deck_sticker.

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

All AIGE tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?