Favro MCP

by truls27a

Overview Schema Source Related Servers Discussions Admin

Python

Remote

list_boards

Retrieve top-level boards or those inside a collection by providing the collection's name or ID.

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:

First call list_collections to see available collections
Then call list_boards with the collection name or ID

Input Schema

TableJSON Schema

Name	Required	Description	Default
`collection`	No	Collection (folder) name or ID. If not provided, only top-level boards are returned.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.7.2Aug 26, 2026
Removedv0.7.0Jul 21, 2026
Changed2 schema fields changedv0.3.2May 1, 2026
- 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."
```
First observedv0.5.0Feb 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description must carry the burden. It discloses the key behavioral nuance: default returns only top-level boards, and passing a collection changes results. It does not mention pagination, ordering, or error behavior, but the output schema likely covers the return format. The core behavioral difference is transparent.

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?

Three concise sentences front-load the purpose, then outline default behavior and usage steps. No filler or redundancy; every sentence earns its place.

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?

Given the tool's simplicity (one optional parameter) and the presence of an output schema, the description fully covers its usage context. It explains when to use it and the necessary prerequisite step (calling list_collections), which is key for correct invocation.

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?

The input schema already provides 100% coverage of the 'collection' parameter, including its default behavior. The description repeats this but adds a usage flow rather than new semantic meaning. With schema coverage at 100%, a baseline of 3 is appropriate.

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 clearly states the verb and resource ('List boards in the organization') and specifies the scope with top-level vs. inside collections. It implicitly differentiates from sibling tools like list_collections by focusing on boards.

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 explains the default behavior (top-level only) and provides step-by-step instructions for listing boards inside a collection, prescribing a two-call sequence with list_collections. This gives clear guidance on when and how to use the tool versus alternatives.

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