Skip to main content
Glama
Sign In

Soleil Clusters

by com.soleilpictures
OverviewDiscussionsAdmin

Move cards

move_cards
Destructive

MOVES cards from one cluster to another: they stop being on the source and are laid out on the destination so they do not overlap what is there. Use it to move cards between clusters; to arrange cards inside one cluster use arrange_board.

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": {
      "from_board_id": "<from_board_id>",
      "to_board_id": "<to_board_id>",
      "card_ids": "<card_ids>"
    },
    "name": "move_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNoThe draft key create_boards returned. Pass it on every call about that draft.
card_idsYesThe cards to move, by id (from read_board)
to_board_idYesWhere they should go
from_board_idYesWhere the cards are now

Output Schema

NameRequiredDescriptionDefault
cardsNo
movedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / draft
      Added value: +{
+  "description": "The draft key create_boards returned. Pass it on every call about that draft.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description still adds real context: that cards are removed from the source (the destructive effect explained) and that layout on the destination is auto-arranged to avoid overlap, which the agent could not infer from annotations alone. It stops short of noting preconditions such as cards having to exist on the source board or whether a moved card keeps its id.

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, zero waste: the effect is front-loaded in the first clause and the sibling disambiguation follows. No restating of the title or 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?

For a 4-parameter mutation tool, the definition covers purpose, side effect, and routing to the correct alternative, while annotations supply the safety profile and a dedicated output schema exists for return values. 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.

Parameters3/5

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

Schema description coverage is 100%, including per-field notes ("The draft key create_boards returned", "by id (from read_board)", "Where the cards are now"), so the schema carries parameter meaning. The description only echoes the from/to relationship implied by "from one cluster to another" and adds nothing on the multi-card card_ids array or draft propagation. Baseline 3 is appropriate.

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 specific verb and resource ("MOVES cards") plus the exact scope and effect: cards leave the source cluster and are laid out on the destination without overlapping existing content. The sibling arrange_board is named as a contrast, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use (moving cards between clusters) and a when-to-use-instead (arranging cards inside one cluster → arrange_board). No inference required to pick the right tool.

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

All Soleil Clusters toolsInspect
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