Skip to main content
Glama
Sign In

Soleil Clusters

by com.soleilpictures
OverviewDiscussionsAdmin

Delete cards

delete_cards
DestructiveIdempotent

DELETES cards from one board. This removes the user's content: confirm with them first. Removed cards are returned; passing them to add_cards restores them (under new ids), except kinds add_cards does not create (grids, palettes, cluster cards, ...) and docs written in the app, which the answer lists in not_restorable: only Version history brings those back.

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": {
      "board_id": "<board_id>",
      "card_ids": "<card_ids>"
    },
    "name": "delete_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNoThe draft key create_boards returned. Pass it on every call about that draft.
board_idYesThe board
card_idsYesThe cards to delete

Output Schema

NameRequiredDescriptionDefault
cardsNo
deletedNo
not_foundNo
untrustedNo

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.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes well beyond them: it warns that user content is destroyed, requires confirmation, states that removed cards are returned for restoration, and enumerates the non-restorable cases (grids, palettes, cluster cards, in-app docs listed in not_restorable) with Version history as the only recovery. That is exactly the nuance an agent needs before invoking a destructive tool.

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 destructive verb and confirmation requirement are front-loaded in the first two sentences, with restoration caveats following. The final sentence is dense with nested parentheticals and an ellipsis, which slightly hurts readability, but no sentence is filler.

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 destructive, idempotent, closed-world delete with an output schema, the description covers the safety requirement, the return of removed cards, and the restoration/exception matrix. Since the output schema handles return shape, nothing essential 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 coverage is 100%, so board_id, card_ids, and draft are already documented in the schema. The description adds no extra syntax, format, or constraint detail for those parameters (e.g. the 1000-card limit or partial-failure behavior), so the baseline 3 applies.

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 opens with a specific verb and resource ('DELETES cards') and immediately bounds the scope to 'one board', which separates it from delete_board and from update_cards/move_cards. An agent knows exactly what object is being mutated.

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 a clear interaction rule ('confirm with them first') and names the recovery alternative (add_cards restores removed cards), which is the main sibling an agent would need. It does not explicitly say when to prefer move_cards or update_cards over deletion, so the routing guidance is clear but not exhaustive.

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