Skip to main content
Glama

get_focus

Read-only

Retrieve the Miro board items you marked as focus, including contents of focused frames, so you can start from your current work area and reference other items as needed.

Instructions

Items the user marked as focus (select on the board + click the MiroBridgeMCP icon), including everything inside focused frames. Focus is the part of the board the user is working on now: start from it and prefer it, but it is not a boundary; read or reference other items when the task needs them (old ideas, related frames). Compact items.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's extra value is the definition of focus, how the user establishes it, the frame-containment behavior, and the note that items come back in compact form. The only soft spot is that 'Compact items' is ambiguous about what is trimmed from each item.

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?

Three sentences, front-loaded with the definition, then usage posture, then the payload note. The parenthetical '(select on the board + click the MiroBridgeMCP icon)' is useful, but the trailing fragment 'Compact items.' is under-specified for the amount of emphasis it gets by standing alone.

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 no parameters, no output schema, and annotations already declaring read-only safety, the description covers what an agent needs to decide to call it and how to interpret the result set. Only the shape of a 'compact item' is left unstated, which is a minor gap rather than a blocking one.

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 takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. Nothing about argument usage is missing or misleading.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description defines the exact result set: items the user marked as focus via board selection plus the MiroBridgeMCP icon, and it explicitly includes everything inside focused frames. It distinguishes this set conceptually from the rest of the board ('not a boundary'), though it never names the sibling retrievers (get_items, get_selection) it overlaps with.

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?

Clear when-to-use direction: 'start from it and prefer it' makes this the default starting read. It also supplies an explicit when-not-to-bound: 'it is not a boundary; read or reference other items when the task needs them (old ideas, related frames)'. It stops short of naming which alternative tool to call in those cases.

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