Skip to main content
Glama

Swap two carousel slides' images

flypost_swap_slide_images

Swap the images of two slides of the same carousel. Both slides must have an image. The image keeps its crop. Slide ids come from flypost_view_visuals; check the result there afterwards.

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": {
      "content_bank_item_id": "<content_bank_item_id>",
      "from_slide_id": "<from_slide_id>",
      "to_slide_id": "<to_slide_id>"
    },
    "name": "flypost_swap_slide_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_slide_idYes
from_slide_idYes
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real value with the precondition and the crop-preservation guarantee, but says nothing about failure behavior when a slide lacks an image or whether slide order/content is otherwise untouched.

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?

Three short sentences, front-loaded with the operation, then the precondition, then the id source and verification. No redundant wording; only the slightly clipped 'The image keeps its crop' sentence reads as terse rather than polished.

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?

With no output schema, the description correctly tells the agent to verify via flypost_view_visuals, implying no meaningful return payload. Preconditions and id sourcing are covered; error/failure semantics are the only notable omission for a mutation tool.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains where slide ids come from (flypost_view_visuals) and implies content_bank_item_id via 'same carousel', but never names or disambiguates from_slide_id/to_slide_id or content_bank_item_id explicitly.

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?

States a precise verb and resource ('Swap the images of two slides') plus a scope constraint ('of the same carousel'). The verb 'swap' is inherently distinguishable from sibling operations like move_slide_image, copy_slide_image, and reuse_slide_image without needing the schema.

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?

Gives a hard precondition ('Both slides must have an image') and routes the agent to flypost_view_visuals for slide ids and for verifying the result afterwards. It stops short of stating when to prefer this over move/copy alternatives, so it is clear context rather than a full when/when-not rule.

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.