Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

get_columns

Retrieve all columns from a specified card table within a project using Basecamp 3 integration. Requires project ID and card table ID for targeted data access.

Instructions

Get all columns in a card table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_table_idYesThe card table ID
project_idYesThe project ID

Implementation Reference

  • MCP tool handler for 'get_columns' that invokes the Basecamp client method and formats the response as MCP content.
    case 'get_columns': {
      const columns = await client.getColumns(typedArgs.project_id, typedArgs.card_table_id);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            status: 'success',
            columns,
            count: columns.length
          }, null, 2)
        }]
      };
    }
  • Input schema definition for the 'get_columns' tool, specifying required project_id and card_table_id parameters.
      name: 'get_columns',
      description: 'Get all columns in a card table',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'The project ID' },
          card_table_id: { type: 'string', description: 'The card table ID' },
        },
        required: ['project_id', 'card_table_id'],
      },
    },
  • Core implementation of getColumns in BasecampClient, fetching card table details and extracting the lists (columns).
    async getColumns(projectId: string, cardTableId: string): Promise<Column[]> {
      const cardTableDetails = await this.getCardTableDetails(projectId, cardTableId);
      return cardTableDetails.lists || [];
    }
  • Supporting method getCardTableDetails used by getColumns to fetch card table data 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 full burden but only states the basic action without behavioral details. It doesn't disclose whether this is a read-only operation, potential rate limits, authentication needs, error conditions, or return format (e.g., list structure), which are critical for a tool with parameters.

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 with zero waste. It's front-loaded and appropriately sized for a simple retrieval tool, making it easy 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 tool has 2 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, or error handling, which are necessary for effective use, especially without structured support.

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?

Schema description coverage is 100%, with both parameters ('card_table_id', 'project_id') documented in the schema. The description implies these are needed to identify the table but adds no extra meaning beyond what the schema provides, meeting the baseline for high coverage.

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') and resource ('all columns in a card table'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_card_table' or 'get_cards' that also retrieve related data, missing explicit 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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., needing a valid card table ID) or comparisons to other retrieval tools in the sibling list, leaving usage unclear.

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