Skip to main content
Glama
Sign In

Soleil Clusters

by com.soleilpictures
OverviewDiscussionsAdmin

Delete board

delete_board
DestructiveIdempotent

DELETES a whole board, its cards and the boards inside it: confirm with the user first. Recoverable: restore_board brings it back within 30 days; list_boards with deleted true finds it. A deleted cluster stops counting toward the card limit at once, so the restore is refused if that room gets used.

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>"
    },
    "name": "delete_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYesThe board

Output Schema

NameRequiredDescriptionDefault
boardNo
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description still adds substantial non-annotated behavior: cascading deletion of cards and sub-boards, a 30-day recovery window, and the card-limit accounting rule that can cause a restore to be refused. That last detail is a genuinely non-obvious side effect an agent could not infer from any structured field.

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 action is front-loaded in caps and every sentence carries new information, with no filler. The final sentence about the card limit is dense and slightly tangled ("if that room gets used"), costing a little readability.

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 one-parameter destructive tool with an output schema, the definition covers purpose, required user confirmation, reversibility window, recovery and discovery alternatives, and a subtle failure mode for restore. Nothing an agent needs before calling 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?

There is a single parameter with 100% schema coverage ("The board", uuid format), so the schema already carries its meaning. The description adds nothing about the identifier itself, which is acceptable here but not creditworthy.

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?

"DELETES a whole board, its cards and the boards inside it" gives a specific verb plus the full blast radius of the resource, which separates it cleanly from delete_cards and delete_group in the sibling list. An agent can tell what it destroys without opening 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 Guidelines5/5

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

Explicitly instructs "confirm with the user first" and routes the agent to concrete alternatives: restore_board for undo and list_boards with deleted true for finding the removed board. It also names the one condition under which the undo path is unavailable, which is exactly the kind of when-not guidance most definitions omit.

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