Soleil Clusters

Import from URLs

import_urls

Idempotent

BRINGS IN reference from the web, each item its own https URL. Images are downloaded and stored, a title becoming the picture's caption; anything else becomes a link card to the original. Safe to run twice: each card is stamped with its source URL, so a repeat run updates the same cards. dry_run first for a long list. For pictures on the web use this, not upload_image.

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

Input Schema

Name	Required	Description
`urls`	Yes	At most 100 https URLs, each a string or {url, title?, group?}
`draft`	No	The draft key create_boards returned. Pass it on every call about that draft.
`group`	No	The section they go in unless their own group says otherwise (made if missing)
`layout`	No	Default justified
`titles`	No	Titles by position in urls; left out, from filenames
`dry_run`	No	Check the list; fetch and create nothing
`board_id`	Yes	The board to import into

Output Schema

Name	Required	Description	Default
`items`	No
`failed`	No
`updated`	No
`imported`	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.3/5.0

Behavior4/5

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

The annotations already declare openWorldHint, non-read-only, idempotent and non-destructive, but the description adds real substance: it explains *why* repeat runs are safe (each card is stamped with its source URL so a rerun updates the same card) and what the tool actually creates. It does not cover what happens when individual URLs fail to fetch or how partial failures are reported, which matters for a 100-URL open-world import, so it stops short of a 5.

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?

Front-loaded with the core action and effect, then idempotency, then the dry_run tactic, then the sibling exclusion — a sensible ordering with no filler. The telegraphic phrasing ("BRINGS IN reference from the web") is slightly awkward and costs a point versus a cleanly written equivalent of the same length.

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 7-parameter, open-world write tool with an output schema, the description supplies the key semantics an agent needs: what gets created per URL, the idempotency guarantee, and the dry_run safety valve. Return values need not be described because an output schema exists; only failure handling for individual URLs is left implicit.

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%, so every parameter is already documented in the schema (including the string-or-object url form, group, title and dry_run). The description echoes the title-as-caption behavior and the dry_run workflow but adds no new syntax or format meaning beyond that. Baseline 3 is correct when the schema carries the parameter burden.

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 (imports web references via https URLs) and immediately explains the two resulting outcomes: images get downloaded and stored as pictures with the title as caption, everything else becomes a link card to the original. It also names the sibling it is not for (upload_image), so an agent can separate the two 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 Guidelines5/5

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

Gives explicit operational guidance: run dry_run first for a long list, and use this tool rather than upload_image for pictures on the web. Both the when-to-use and the when-to-use-something-else cases are covered directly.

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.