Skip to main content
Glama
Sign In

Soleil Clusters

by com.soleilpictures
OverviewDiscussionsAdmin

Restore board

restore_board
Idempotent

Puts a deleted board back, with its cards and the boards inside it. If its parent is still deleted, it comes back under the nearest one that is not. list_boards with deleted true lists what can be restored.

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": "restore_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYesThe board

Output Schema

NameRequiredDescriptionDefault
urlNo
boardNo
restoredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 non-read-only, idempotent, non-destructive, but the description adds real behavior the annotations cannot: the restore is recursive over cards and child boards, and an orphaned parent causes reattachment to the nearest non-deleted ancestor. That cascade and fallback rule is exactly the kind of consequence an agent needs before calling a restore.

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?

Three short sentences with no filler: the action first, the edge-case rule second, the discovery pointer last. Every sentence supplies information an agent would otherwise have to guess.

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 one-parameter tool with annotations and an output schema, this covers action, cascade scope, and the orphaned-parent edge case. It leaves out failure behavior for an id that is not deleted and any permission requirements, which are the only remaining gaps.

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% and the single parameter is already documented as 'The board' with a uuid format, so the schema carries the load. The description only implicitly narrows the id to a deleted board; it adds no format, aliasing, or resolution detail beyond the schema baseline.

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 ('Puts a deleted board back') and immediately bounds the scope of the operation to the board's cards and contained sub-boards. It is unmistakably distinct from delete_board and update_boards, and an agent could pick it without opening a 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?

Routes discovery explicitly to a sibling: 'list_boards with deleted true lists what can be restored,' which is genuine when-to-use guidance. It stops short of stating an exclusion (e.g. what happens if the board is not deleted), so it is clear context rather than a full when/when-not pair.

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