Skip to main content
Glama
truls27a

Favro MCP

by truls27a
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

assign_card

Assign or unassign a user to a Favro card using card ID, sequential ID, or name. Specify user by ID, name, or email, and choose to add or remove the assignment.

Instructions

Assign or unassign a user from a card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardYesCard ID, sequential ID (#123), or name
userYesUser ID, name, or email
boardNoBoard ID or name (needed for name lookups)
removeNoIf True, remove the assignment instead of adding

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / board / description
      Added value: +"Board ID or name (needed for name lookups)"
    • addedInput schema / properties / card / description
      Added value: +"Card ID, sequential ID (#123), or name"
    • addedInput schema / properties / remove / description
      Added value: +"If True, remove the assignment instead of adding"
    • addedInput schema / properties / user / description
      Added value: +"User ID, name, or email"
  2. First observedv0.5.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It covers the basic behaviors of assignment and unassignment but does not disclose potential side effects, error conditions, or required permissions.

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?

The description is a single, direct sentence of 12 words, front-loaded with the essential action. Every word is meaningful.

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 simple tool with few parameters and an output schema (not shown), the description covers the main action adequately. Missing details about error handling are minor given the tool's straightforward nature.

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% with descriptions for all four parameters. The description adds little beyond the schema, essentially summarizing the operation, so it meets the baseline for high coverage.

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 'Assign or unassign a user from a card' clearly specifies the verb (assign/unassign) and resource (user, card). It distinguishes this tool from siblings like create_card or update_card by focusing on user assignment.

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

Usage Guidelines3/5

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

The description implies usage for adding or removing user assignments but does not explicitly state when to use this tool versus alternatives, nor does it provide conditions or prerequisites.

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