Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

get_selection

Read-onlyIdempotent

Retrieve selected element IDs and blueprint data from a canvas; large selections are summarized with counts, bounds, and IDs so you can read full subtrees.

Instructions

Get the IDs and blueprint of currently selected elements on a specific canvas. Returns selected element IDs and their blueprint representation including descendants. A selection past 1,000 elements (descendants included) is summarized: counts by type (countsByType), union bounds (worldBounds), the first 100 ids and a note, beside the true count. Use read with a scope of ids or #refs for full subtrees. (External MCP clients: call init first for usage docs. Hosted-CLI and sub-agents have docs pre-loaded.)

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": {
      "canvasId": "<canvasId>"
    },
    "name": "get_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoOptional: run THIS call against a project other than the session's bound one: a name or key from list_projects (or an unambiguous name/handle substring), or the absolute path of a project folder (one holding .bl files, or an empty one), which opens in the background and is added to list_projects. Unknown/ambiguous is refused with candidates.
canvasIdYesCanvas ID to get selection from. REQUIRED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower, yet the description still discloses the non-obvious truncation contract: counts by type, union world bounds, first 100 ids, a note, and the true count. That degradation behavior is exactly what an agent needs to know before trusting the result as complete.

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 purpose, then the return contract, then the fallback tool, then the setup note — a sensible priority order with no filler sentences. The trailing init parenthesis is slightly generic boilerplate, keeping it just under a 5.

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?

With no output schema, the description carries the return-value burden and does so: it names the returned fields, explains the summarized shape and its thresholds, and points to the tool that returns full subtrees. Nothing an agent needs to call this correctly 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?

Schema coverage is 100%, so canvasId and project are already fully self-documenting, and the description adds no syntax, format, or sourcing detail beyond the schema. Baseline 3 applies because the schema is doing all the parameter work.

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 ('Get the IDs and blueprint of currently selected elements') plus a scope qualifier ('on a specific canvas'), which immediately separates it from bulk-read siblings like read or objects_result.

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 concrete routing advice: when the selection exceeds 1,000 elements the result is summarized, and 'Use read with a scope of ids or #refs for full subtrees' names both the alternative and the condition that selects it. It also states the prerequisite for external MCP clients ('call init first'), covering the when-not case.

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