Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

get_card_table

Retrieve card table details for a specific project by providing the project ID. Integrates with Basecamp 3 to manage project-related data efficiently.

Instructions

Get the card table details for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe project ID

Implementation Reference

  • Main handler for the 'get_card_table' MCP tool. Fetches the card table for a project using BasecampClient methods and returns JSON-formatted details.
    case 'get_card_table': {
      const cardTable = await client.getCardTable(typedArgs.project_id);
      const cardTableDetails = await client.getCardTableDetails(typedArgs.project_id, cardTable.id);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            status: 'success',
            card_table: cardTableDetails
          }, null, 2)
        }]
      };
    }
  • src/index.ts:178-187 (registration)
    Tool registration in the listTools handler, including name, description, and input schema.
      name: 'get_card_table',
      description: 'Get the card table details for a project',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'The project ID' },
        },
        required: ['project_id'],
      },
    },
  • Input schema definition for the get_card_table tool.
    inputSchema: {
      type: 'object',
      properties: {
        project_id: { type: 'string', description: 'The project ID' },
      },
      required: ['project_id'],
    },
  • Helper method to retrieve the first card table for a project.
    async getCardTable(projectId: string): Promise<any> {
      const cardTables = await this.getCardTables(projectId);
      if (!cardTables.length) {
        throw new Error(`No card tables found for project: ${projectId}`);
      }
      return cardTables[0];
    }
  • Helper method to fetch detailed card table information via API.
    async getCardTableDetails(projectId: string, cardTableId: string): Promise<CardTable> {
      try {
        const response = await this.client.get(`/buckets/${projectId}/card_tables/${cardTableId}.json`);
        return response.data;
      } catch (error: any) {
        if (error.response?.status === 204) {
          return { id: cardTableId, title: 'Card Table', lists: [], status: 'empty' };
        }
        throw error;
      }
    }
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 implies a read operation ('Get'), but doesn't specify if it requires authentication, has rate limits, returns paginated results, or what the output format looks like. For a tool with no annotation coverage, this leaves significant behavioral aspects unclear.

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, straightforward sentence that efficiently conveys the core action. It is front-loaded with the main purpose and avoids unnecessary words, making it appropriately concise for a simple tool. However, it could be slightly more structured by including key usage details.

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 insufficiently complete. It doesn't explain what 'card table details' entail, how the data is returned, or any error conditions. For a tool in a context with many sibling tools and no structured output, more detail is needed to guide effective use.

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 'project_id' clearly documented in the schema. The description adds no additional meaning beyond implying the parameter is used to fetch card table details for a specific project, which aligns with the schema. Baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 verb 'Get' and the resource 'card table details for a project', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_cards' or 'get_card', which might retrieve similar but different data, leaving some ambiguity about what exactly 'card table details' includes compared to other get operations.

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 'get_cards' or 'get_card', nor does it mention any prerequisites or context for usage. It simply states what the tool does without indicating scenarios or constraints for its application.

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

Related 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/jhliberty/basecamp-mcp-server'

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