Skip to main content
Glama

List my boards

list_my_boards
Read-onlyIdempotent

Find the user's personal boards, including private ones, and organisation boards they can access when this connection has read:org consent. Returns name, handle/slug, visibility, schematic/pcb availability, last updated and URL, newest first. Needs personal-board consent. Then use get_board, read_schematic, read_pcb, get_bom or read_file on a returned reference. When the user has no boards yet, the result carries nextSteps in the order to offer them: the ways to add a board from here when this connection can store one, then a public-library search that works right away. search_boards searches public boards only. If organisation boards are missing, reconnect with 'Include organisation boards' selected.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structural behavior: consent prerequisites (personal-board consent, read:org), result ordering (newest first), and the conditional nextSteps payload returned when the user has no boards. It does not discuss limits, caching, or failure modes beyond the org-consent case, so it falls just short of 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?

It is dense but front-loaded: purpose and scope come first, then routing, then edge cases. The one wasteful element is enumerating return fields ("name, handle/slug, visibility, schematic/pcb availability, last updated and URL") when an output schema already exists, which duplicates structured data.

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?

Given the zero-parameter schema, full annotation coverage, and an existing output schema, the description supplies everything needed to select and call the tool: consent preconditions, alternatives, and the empty-state behavior. Slight over-coverage on return fields rather than a real gap.

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 there are no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing filter arguments, though it also does not warn that no filtering is possible (e.g. that paging or scoping must be done client-side).

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?

The description gives a specific verb and resource ("Find the user's personal boards") and precisely scopes it as personal/private boards plus organisation boards under read:org consent. It explicitly contrasts with the sibling search_boards ("searches public boards only"), so an agent can distinguish the two without opening either 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?

It states follow-on routing explicitly ("Then use get_board, read_schematic, read_pcb, get_bom or read_file on a returned reference") and names the exclusion case via search_boards for public boards. It also covers a recovery path: reconnect with 'Include organisation boards' selected when org boards are missing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources