Skip to main content
Glama
truls27a

Favro MCP

by truls27a
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Cards

list_cards

Retrieve cards from a specific Favro board with pagination, optionally filtering by column or archived status.

Instructions

List cards on a specific board with pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (0-indexed, default 0). Each page contains up to 100 cards.
boardYesThe board's widget_common_id, name, or ID
columnNoOptional column ID or name to filter by. The cards then come back in the order they have in the column, top first.
archivedNoFilter by archived status. True = only archived, False = only non-archived, None = all (default).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / column / description
      Previous value: -"Optional column ID or name to filter by"New value: +"Optional column ID or name to filter by. The cards then come\nback in the order they have in the column, top first."
  2. Changed5 schema fields changedv0.3.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / archived
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by archived status. True = only archived, False = only non-archived, None = all (default)."
+}
    • addedInput schema / properties / board / description
      Added value: +"The board's widget_common_id, name, or ID"
    • addedInput schema / properties / column / description
      Added value: +"Optional column ID or name to filter by"
    • addedInput schema / properties / page / description
      Added value: +"Page number (0-indexed, default 0). Each page contains up to 100 cards."
  3. First observedv0.5.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses pagination, which is useful, but omits anything about permissions/auth, ordering defaults, or rate limits for a list operation. With zero annotation coverage and an output schema present, the description still leaves key behavioral context unstated.

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?

A single efficient sentence with the resource and scoping front-loaded and no wasted words. It is arguably too terse for the tool's complexity, but as pure conciseness it is clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need not be explained. The 100% schema coverage documents parameters well, but for a 4-parameter list tool with no annotations, the description does not address filtering behavior or usage context sufficiently to be fully complete.

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%, so the schema already documents board, column, page, and archived with clear semantics (0-indexed pages, archived tri-state, column ordering). The description adds nothing beyond this, so the baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb 'List' and resource 'cards', and scopes it to 'a specific board with pagination', so an agent can distinguish it from sibling single-card tool get_card_details. However, it doesn't position itself against other list tools (list_boards, list_columns), so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description says what the tool does but gives no when-to-use/when-not guidance and names no alternatives. It never indicates that get_card_details should be used for a single card or that list_columns can be used to discover columns for filtering.

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