Skip to main content
Glama

get_card

Retrieve detailed information about a specific task card using its unique ID to access content, status, and properties in Focalboard.

Instructions

Get detailed information about a specific card by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardIdYesThe ID of the card to retrieve

Implementation Reference

  • The main execution handler for the 'get_card' MCP tool. It validates the cardId input, calls FocalboardClient.getCard(), and formats the response as MCP content.
    case 'get_card': {
      const cardId = args?.cardId as string;
      if (!cardId) {
        throw new Error('cardId is required');
      }
      const card = await focalboard.getCard(cardId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(card, null, 2)
          }
        ]
      };
    }
  • src/index.ts:132-145 (registration)
    Tool registration definition for 'get_card' including name, description, and input schema used by MCP server for listing and validation.
    {
      name: 'get_card',
      description: 'Get detailed information about a specific card by its ID.',
      inputSchema: {
        type: 'object',
        properties: {
          cardId: {
            type: 'string',
            description: 'The ID of the card to retrieve'
          }
        },
        required: ['cardId']
      }
    },
  • Core helper method in FocalboardClient that performs the HTTP API request to fetch the specific card by ID.
    async getCard(cardId: string): Promise<Card> {
      return this.makeRequest<Card>(`/cards/${cardId}`);
    }
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 but offers minimal information. It mentions retrieving 'detailed information' but doesn't specify what that includes, whether authentication is required, potential rate limits, error conditions, or if the operation is idempotent. For a read operation with zero annotation coverage, this leaves significant behavioral gaps.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what 'detailed information' includes, how results are structured, or any behavioral constraints. For a tool with no structured metadata, the description should provide more context about the operation's scope and limitations.

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 schema description coverage is 100%, with the single parameter 'cardId' clearly documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline score of 3 where the schema does the heavy lifting for parameter 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 clearly states the action ('Get detailed information') and resource ('about a specific card by its ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_card_content' or 'get_cards', which also retrieve card-related information, so it doesn't achieve the highest level of sibling distinction.

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 'get_card_content' or 'get_cards'. It simply states what the tool does without indicating appropriate contexts, prerequisites, or exclusions, leaving the agent to infer usage patterns from the tool name alone.

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