trello-guardrails-mcp

Overview Schema Source Related Servers Discussions Admin

Update Card

update_card

Update a Trello card's name, description, or due date by specifying its board and card name. Leave fields empty to keep existing values.

Instructions

Update a card's name, description, or due date (ISO 8601, e.g. 2026-05-15). Leave fields empty to keep them unchanged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "board_name": "<board_name>",
      "card_name": "<card_name>"
    },
    "name": "update_card"
  }
}

Input Schema

Name	Required	Description	Default
`due_date`	No
`new_name`	No
`card_name`	Yes
`board_name`	Yes
`new_description`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It adds the important partial-update semantics (empty fields are no-ops) and the ISO 8601 date format requirement, which are real behavioral traits beyond the tool name. However, it does not mention whether updates are destructive, require permissions, or affect other card fields, leaving notable gaps for a mutation tool.

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 description is a single, dense sentence that front-loads the verb, resource, and fields, then adds the format and behavior. It contains no fluff and every clause adds value. Slightly more structure could include the identifying parameters, but as written it is efficient and readable.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, but the description leaves major gaps for a mutation tool. It does not explain how the card is identified via board_name and card_name, which are required parameters, nor does it note prerequisites like an existing card/board or error conditions. The description addresses the update fields but not the targeting mechanism, making it incomplete for safe 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?

Schema description coverage is 0%, so the description must compensate. It maps 'name, description, due date' to new_name, new_description, and due_date, and adds the empty-field meaning. However, it does not explain the required identifiers board_name and card_name, which are essential for the agent to target the correct card. The description covers only 3 of 5 parameters meaningfully.

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 tool updates a card's name, description, or due date, with a specific verb and resource. It differentiates from siblings like create_card, archive_card, and move_card by explicitly listing the updatable fields, so an agent can identify the correct operation.

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?

The description gives clear context for when to use it: when changing one or more of the three named fields. It also provides a usage rule, 'Leave fields empty to keep them unchanged,' which guides the agent on how to perform a partial update. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear.

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

Deploy Server