Skip to main content
Glama

add_card_description

Add descriptive content to Focalboard cards using markdown formatting to document tasks, provide context, or attach detailed information directly within cards.

Instructions

Add or set description/content to a card. Creates a new text block with markdown content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardIdYesThe ID of the card to add description to
boardIdYesThe ID of the board the card belongs to
descriptionYesThe description content in markdown format

Implementation Reference

  • src/index.ts:197-218 (registration)
    Tool registration entry defining the name, description, and input schema for 'add_card_description'.
    {
      name: 'add_card_description',
      description: 'Add or set description/content to a card. Creates a new text block with markdown content.',
      inputSchema: {
        type: 'object',
        properties: {
          cardId: {
            type: 'string',
            description: 'The ID of the card to add description to'
          },
          boardId: {
            type: 'string',
            description: 'The ID of the board the card belongs to'
          },
          description: {
            type: 'string',
            description: 'The description content in markdown format'
          }
        },
        required: ['cardId', 'boardId', 'description']
      }
    },
  • Handler logic for executing the 'add_card_description' tool: validates parameters, sets the description using the Focalboard client, retrieves the updated card, and returns it as JSON.
    case 'add_card_description': {
      const cardId = args?.cardId as string;
      const boardId = args?.boardId as string;
      const description = args?.description as string;
    
      if (!cardId || !boardId || !description) {
        throw new Error('cardId, boardId, and description are required');
      }
    
      await focalboard.setCardDescription(boardId, cardId, description);
      const card = await focalboard.getCard(cardId);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(card, null, 2)
          }
        ]
      };
    }
  • Core helper function that implements the description setting logic: checks for existing text block and updates it, or creates a new one if none exists.
    async setCardDescription(boardId: string, cardId: string, description: string): Promise<Block> {
      // Get existing content blocks
      const contentBlocks = await this.getCardContent(cardId);
      const textBlocks = contentBlocks.filter(block => block.type === 'text');
    
      if (textBlocks.length > 0) {
        // Update the first text block directly
        const textBlock = textBlocks[0];
        await this.makeRequest<void>(
          `/boards/${boardId}/blocks/${textBlock.id}`,
          'PATCH',
          { title: description }
        );
    
        // Fetch and return the updated block
        const updatedBlocks = await this.makeRequest<Block[]>(
          `/boards/${boardId}/blocks`,
          'GET',
          undefined,
          { block_id: textBlock.id }
        );
        return updatedBlocks[0];
      } else {
        // Create a new text block
        return this.createTextBlock(boardId, cardId, description);
      }
    }
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 burden of behavioral disclosure. It mentions that the tool 'creates a new text block with markdown content,' which implies a write operation but does not specify permissions needed, whether it overwrites existing content, error handling, or other behavioral traits like rate limits or side effects. 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 a single, efficient sentence that front-loads the core action ('Add or set description/content to a card') and adds necessary detail ('Creates a new text block with markdown content') without redundancy. It is appropriately sized with zero waste, making it easy to parse quickly.

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?

Given the tool's complexity as a mutation operation with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose and parameter hints but lacks details on behavioral aspects, error cases, or return values. For a tool that modifies data, more context would be beneficial to ensure safe and correct usage.

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?

The input schema has 100% description coverage, clearly documenting all three required parameters (cardId, boardId, description). The description adds minimal value beyond the schema by implying the 'description' parameter uses markdown format, but this is already stated in the schema. With high schema coverage, the baseline score of 3 is appropriate as the description does not significantly enhance parameter understanding.

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 ('Add or set description/content') and the target resource ('to a card'), specifying it creates a new text block with markdown content. However, it does not explicitly differentiate from sibling tools like 'update_card' or 'get_card_content', which might handle similar card modifications or retrievals, leaving some ambiguity in sibling differentiation.

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 such as 'update_card' (which might also modify card properties) or 'get_card_content' (which retrieves content). It lacks explicit context, prerequisites, or exclusions, offering only a basic functional statement without usage scenarios.

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/gmjuhasz/focalboard-mcp-server'

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