Skip to main content
Glama

get_board_info

Read-only

Retrieve a lightweight Miro board overview with board ID, item counts by type, frame details, and focus status. Use it first to plan targeted reads via focus or parent filters.

Instructions

Cheap overview: board id, item counts by type, frames {id, title, children}, and whether the user set a focus. Call this first instead of reading the whole board, then get_focus or get_items with parentId.

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_board_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond them: the cost profile ('cheap') and the role this call plays as a discovery step in a two-phase workflow. It does not state whether output is paginated or bounded for large boards, which is the only notable gap.

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?

A single dense sentence plus a usage clause, with the value proposition front-loaded ahead of the follow-up routing. The brace shorthand for frame fields is compact without being ambiguous. No filler.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does so by naming each returned element. Combined with the follow-up routing to get_focus and get_items, an agent has everything needed to call this correctly on the first try.

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 schema takes zero parameters, so there is no parameter semantics to explain; the baseline for a 0-param tool applies. The description correctly spends its words on return shape and sequencing instead of restating an empty input object.

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 ('overview') and enumerates exactly what is returned: board id, item counts by type, frames with id/title/children, and focus state. 'Cheap overview' plus the field list distinguishes it clearly from get_items, which returns the full contents.

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 an explicit ordering rule ('Call this first instead of reading the whole board') and names the concrete follow-up paths ('then get_focus or get_items with parentId'). Both the when and the what-next are stated, leaving nothing to inference.

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