Skip to main content
Glama
truls27a

Favro MCP

by truls27a
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Boards

list_boards

Retrieve Favro boards at top level by default, or specify a collection name/ID to retrieve boards inside folders.

Instructions

List boards in the organization.

By default, lists boards at the TOP LEVEL only (not inside collections/folders).

To find boards inside a collection:

  1. First call list_collections to see available collections

  2. Then call list_boards with the collection name or ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionNoCollection (folder) name or ID. If not provided, only top-level boards are returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2
  2. Removedv0.7.0
  3. Changed2 schema fields changedv0.3.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / collection / description
      Added value: +"Collection (folder) name or ID. If not provided,\n       only top-level boards are returned."
  4. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the critical non-obvious trait that results are scoped to top-level boards by default, but does not mention pagination, result limits, or whether an empty result means 'no boards' vs 'no top-level boards'.

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?

Front-loads the scope constraint in the first line, then uses a short numbered list for the workflow. Every sentence earns its place with zero 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?

An output schema exists, so return-shape detail is unnecessary, and the description covers both scope and the collection traversal path. The only remaining gap is pagination/limit behavior, which is a minor omission for a list tool.

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 coverage is 100% and the single 'collection' parameter is fully documented in the schema, so the baseline is 3. The description reinforces the param's meaning (name or ID, default = top-level) and adds workflow context, but introduces no syntax or format detail beyond the schema.

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 and resource ('List boards in the organization') and immediately clarifies scope: top-level by default, not inside collections. This distinguishes it cleanly from the collection-oriented siblings and an agent can tell what it returns without opening the 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?

Explicitly describes default behavior (top-level only) and provides a concrete two-step workflow routing through list_collections to reach boards inside a collection. This is exactly the when/when-not/alternative guidance the dimension asks for.

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

Deploy Server

Other Tools