Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

update_card

Modify Trello card details such as title, description, due date, or labels to keep project tasks current and organized.

Instructions

Update a Trello card

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYes
updatesYes

Implementation Reference

  • The main handler function for the 'update_card' tool. It validates configuration, extracts arguments, and calls the client's updateCard method to perform the update.
    async update_card(args: Record<string, unknown>) {
      if (!cfg.trelloKey || !cfg.trelloToken) throw new Error("TRELLO_KEY/TRELLO_TOKEN are not configured");
      const cardId = String(args.card_id || "");
      if (!cardId) throw new Error("card_id is required");
      const updates = (args.updates as Record<string, unknown>) || {};
      return client.updateCard(cardId, updates);
    },
  • Tool registration for 'update_card', including name, description, and input schema definition.
    {
      name: "update_card",
      description: "Update a Trello card",
      inputSchema: {
        type: "object",
        properties: {
          card_id: { type: "string" },
          updates: { type: "object" },
        },
        required: ["card_id", "updates"],
      },
    },
  • Helper method in TrelloClient that performs the actual API request to update a card.
    updateCard(cardId: string, updates: Record<string, unknown>) {
      return this.request(`/cards/${cardId}`, { method: "PUT", query: this.authQuery(updates as any) });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Update' implies a mutation, but it doesn't specify required permissions, whether changes are reversible, rate limits, or what the response looks like. This is inadequate for a mutation tool with zero annotation coverage.

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 'Update a Trello card' is extremely concise and front-loaded, with no wasted words. It efficiently communicates the core purpose in a single, clear sentence.

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?

Given the tool's complexity (mutation with 2 parameters, nested objects, no output schema, and 0% schema coverage), the description is incomplete. It lacks details on parameters, behavioral traits, and output, making it insufficient for effective tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, and the description adds no information about the parameters 'card_id' or 'updates'. It doesn't explain what 'card_id' refers to, what fields 'updates' can include, or provide any examples, failing to compensate for the schema's lack of documentation.

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?

The description 'Update a Trello card' clearly states the verb ('Update') and resource ('Trello card'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling tool 'update_page' or specify what aspects of a card can be updated, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives like 'create_card' or 'update_page'. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/muti-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server