Skip to main content
Glama

get_boards

Read-onlyIdempotent

Los tableros de Tareas que esta persona puede abrir, de los tres tipos que hay.

Un tablero es una vista guardada con nombre: las CONDICIONES dicen de qué
tiene que ser una tarea para entrar (etiquetada con tal cliente, de tal
proyecto), y eso es el tablero. La regla es dinámica — una tarea nueva que
cumpla entra sola, y una a la que le sacan la etiqueta desaparece.

Los tres tipos:
· `privado`    — sólo lo ve su dueño. Vive en las preferencias del usuario,
                  no en una tabla, y su id empieza con `tb`.
· `compartido` — tuyo, pero ya promovido a fila de servidor porque se lo
                  pasaste a alguien. Id uuid.
· `prestado`   — de otra persona, que te lo compartió. Vive en SU workspace
                  y vos no sos miembro de ahí: lo único que podés ver es lo
                  que entra en ese tablero, nada más del workspace.

Un tablero SIN condiciones no se puede compartir (casi todos los de fábrica,
como «Mi semana» o «En curso», no tienen ninguna): sin alcance, compartirlo
sería compartir el workspace entero.

Para ver qué tareas tiene adentro: get_board_tasks.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial semantics beyond them: the rule is dynamic (a new matching task enters, an untagged one leaves), private boards live in user preferences with `tb` ids, shared boards are server rows with uuids, and borrowed boards live in a workspace where the caller is not a member so only board-matching content is visible. It also notes that a board with no conditions cannot be shared, which explains why most factory boards look the way they do. Missing only operational traits such as result ordering or pagination.

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?

The purpose is front-loaded, the three board types are laid out as a scannable list, and the sibling pointer sits at the end where it belongs. It runs long for a one-parameter list tool, and the aside about boards without conditions not being shareable is somewhat tangential to enumeration, but no sentence is pure filler.

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?

For a single-optional-parameter, read-only list tool with no output schema, the description supplies the conceptual model needed to interpret what comes back (types, id formats, visibility limits). What it omits — ordering, result size, and the concrete fields of a board record — is minor given the simplicity and annotation coverage.

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 description coverage is 100% and the single parameter already documents that it accepts a UUID or a plain workspace name and that omitting it queries all workspaces in one call. The description never mentions workspace_id and adds no extra meaning, so the schema carries the parameter semantics entirely — baseline 3.

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?

Opens with a specific verb-and-resource statement: the task boards this person can open, of the three types that exist. It then defines what a board actually is (a named saved view with CONDITIONS) and closes by naming the sibling that returns board contents, so an agent can distinguish get_boards from get_board_tasks without inspecting 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear routing: use this to enumerate boards, use get_board_tasks for the tasks inside a board. It also implies the scope of a call (all boards the person can open, optionally narrowed by workspace). It does not set exclusions against unrelated siblings such as get_agenda or get_entity_tasks, but the task-domain boundary is unambiguous.

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