Soleil Clusters

View pictures

view_board

Read-onlyIdempotent

See a board's pictures as a person does: its overall picture, then its images in reading order, each after a line naming its card id and title. 12 pictures by default, up to 24; card_ids (up to 4) shows some larger. read_board gives text and positions.

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

Input Schema

Name	Required	Description
`draft`	No	The draft key create_boards returned. Pass it on every call about that draft.
`limit`	No	Pictures to show: default 12, max 24
`cursor`	No	From the previous answer, for the next pictures
`board_id`	Yes	The board
`card_ids`	No	Up to 4 cards to look at closely, larger

Output Schema

Name	Required	Description	Default
`board`	No
`has_more`	No
`pictures`	No
`untrusted`	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.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds context instead: default 12 / max 24 pictures and the interleaving of caption lines with images. It does not describe the image format, resolution, or how cursor paging behaves, but the presence of an output schema lowers the burden.

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 dense sentences with the output shape front-loaded and the sibling disambiguation last, which is the right priority order. The 12/24 figures and 'as a person does' phrasing partly repeat or ornament the schema, keeping it from a perfect score.

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 read-only rendering tool with rich annotations, a full output schema, and 100% schema coverage, the description supplies everything an agent needs: what is returned, in what order, the default and max size, and the alternative to use for text data. No significant gap remains.

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 every parameter is already documented, giving a baseline of 3. The description restates limit (12 default, 24 max) and the card_ids 'larger' behavior, which largely duplicates the schema, and it says nothing about draft or cursor beyond what the schema provides.

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?

Names a specific verb and resource ('See a board's pictures') and pins down the exact return order: overall picture first, then images in reading order, each preceded by a line with card id and title. It explicitly separates itself from the sibling read_board ('gives text and positions'), so an agent can choose 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 Guidelines4/5

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

The closing sentence routes the agent to read_board for text and positions, implying this tool is the visual counterpart. The 'card_ids (up to 4) shows some larger' note gives a concrete usage pattern for close inspection. It stops short of explicit 'use this when / not when' framing or stating prerequisites such as draft vs. published boards.

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.