Soleil Clusters

Create group

create_group

CREATES a named group, returns its id. add_cards and update_cards can name a section in group instead (made if missing): use this for a group before its cards exist, or to set its shape.

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

Input Schema

Name	Required	Description
`name`	Yes	What this set of cards is
`color`	No	Outline colour, as add_cards takes color
`draft`	No	The draft key create_boards returned. Pass it on every call about that draft.
`shape`	No	box: one rectangle round everything; hug: follows each card
`board_id`	Yes	The board

Output Schema

Name	Required	Description	Default
`group`	No
`board_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / draft

Added value: +{
+  "description": "The draft key create_boards returned. Pass it on every call about that draft.",
+  "type": "string"
+}

First observedNov 5, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write semantics are covered. The description adds the implicit-creation behavior of siblings, but says nothing about duplicate group names, permissions, or what happens on re-creation — the main behavioral risks for a non-idempotent create.

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?

Two sentences, front-loaded with the verb and return value, with no filler. The second sentence is slightly dense and its grammar ("can name a section in group instead") takes a second read, costing some clarity.

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 an output schema present and full parameter coverage, the description needn't explain returns or field formats, and it correctly covers the decision boundary against siblings. The only meaningful gap left is create-time edge behavior such as name collisions.

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% and every parameter (name, color, shape, board_id, draft) is documented in the schema itself, so the baseline applies. The description only gestures at "shape" ("to set its shape") without adding meaning beyond the enum descriptions already present.

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 ("CREATES a named group") plus the return value ("returns its id"), and explicitly distinguishes it from sibling paths by noting add_cards and update_cards can name a section instead.

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?

Names the alternatives (add_cards, update_cards, which create the section if missing) and gives the two conditions selecting this tool: before the group's cards exist, or to set its shape. An agent can route correctly without opening a sibling schema.

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

All Soleil Clusters tools Inspect

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.