Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

list_capture_targets

Read-onlyIdempotent

Lists the capture-registry IDs mounted in Brilliant's UI so agents can choose valid target, cropTo, and highlight IDs for capture_ui. Returns a sorted JSON array with bounds and nested children.

Instructions

List the capture-registry ids currently mounted in Brilliant's UI (the valid "target"/"cropTo"/highlight ids for capture_ui). Takes no arguments. Returns a sorted JSON array; each entry is {id, mounted, rect: [x, y, w, h] in logical global pixels, children: [nested ids]}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_capture_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds substantial behavior beyond that: no arguments are accepted, the result is a sorted JSON array, and each entry has a fixed shape with rect units explicitly given as logical global pixels and children as nested ids — critical since there is no output schema. This is exactly the kind of value-add the description should carry.

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 compact sentences, front-loaded with the purpose, then the no-argument fact, then the return contract. Every clause carries information an agent needs; nothing is padded or restated from the title.

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 takes on the return-value burden and does so fully: array sortedness, per-entry field names, rect unit semantics, and recursive children. Combined with the annotations covering safety and the zero-parameter schema, an agent has everything required to call and parse this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4, and the description reinforces this with an explicit "Takes no arguments", removing any doubt about whether ids or filters can be supplied. No further parameter meaning is possible or needed.

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 (list) and resource (capture-registry ids mounted in the UI), and immediately clarifies what those ids are for by naming the consuming tool ("the valid target/cropTo/highlight ids for capture_ui"). An agent can distinguish it from capture_ui and from the other list_* siblings without opening any 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 description makes the usage context clear by tying the output to capture_ui's target/cropTo/highlight parameters, which implies calling this first to obtain valid ids. It stops short of an explicit "call this before capture_ui; do not call if you already have ids" statement or any exclusions, so it is clear context rather than full routing guidance.

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