Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

create_card

Add a new card to a Trello list with a name and optional description, enabling task management through the Multi-MCPs server's unified API integration.

Instructions

Create a card in a Trello list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
nameYes
descNo

Implementation Reference

  • The asynchronous handler function for the 'create_card' tool. It validates configuration, extracts list_id, name, and optional desc from args, and delegates to TrelloClient.createCard.
    async create_card(args: Record<string, unknown>) {
      if (!cfg.trelloKey || !cfg.trelloToken) throw new Error("TRELLO_KEY/TRELLO_TOKEN are not configured");
      const listId = String(args.list_id || "");
      const name = String(args.name || "");
      const desc = args.desc ? String(args.desc) : undefined;
      if (!listId || !name) throw new Error("list_id and name are required");
      return client.createCard(listId, name, desc);
    },
  • The tool registration object for 'create_card' within the registerTrello() function, including name, description, and input schema.
    {
      name: "create_card",
      description: "Create a card in a Trello list",
      inputSchema: {
        type: "object",
        properties: {
          list_id: { type: "string" },
          name: { type: "string" },
          desc: { type: "string" },
        },
        required: ["list_id", "name"],
      },
    },
  • Input schema definition for the 'create_card' tool, specifying required list_id and name, optional desc.
    inputSchema: {
      type: "object",
      properties: {
        list_id: { type: "string" },
        name: { type: "string" },
        desc: { type: "string" },
      },
      required: ["list_id", "name"],
    },
  • TrelloClient helper method that performs the actual API request to create a card using POST /cards with authentication and parameters.
    createCard(listId: string, name: string, desc?: string) {
      return this.request(`/cards`, { method: "POST", query: this.authQuery({ idList: listId, name, desc }) });
    }
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. It states this is a creation operation, implying it's a write/mutation tool, but doesn't mention any behavioral traits like required permissions, whether it's idempotent, what happens on duplicate names, or what the response contains. This leaves significant 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just 6 words, front-loading the essential action and resource without any wasted words. Every element earns its place, making it efficient for quick understanding.

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?

For a mutation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It states what the tool does at a high level but lacks crucial details about behavior, parameters, and expected outcomes that would be needed for proper agent usage.

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?

With 0% schema description coverage and 3 parameters, the description provides no information about what 'list_id', 'name', or 'desc' mean, their formats, constraints, or examples. The description doesn't compensate for the complete lack of schema documentation, leaving parameters essentially undocumented.

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 clearly states the action ('Create') and resource ('a card in a Trello list'), making the purpose immediately understandable. However, it doesn't distinguish this from sibling tools like 'update_card' or 'create_issue', which would require more specific differentiation to achieve 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. There's no mention of prerequisites (e.g., needing a list_id), comparison to sibling tools like 'update_card', or scenarios where this is appropriate versus other creation tools like 'create_issue' or 'create_playlist'.

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