Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

get_campfire_lines

Retrieve recent messages from a Basecamp campfire chat room by specifying the project ID and campfire ID to stay updated on team discussions and collaboration.

Instructions

Get recent messages from a Basecamp campfire (chat room)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campfire_idYesThe campfire/chat room ID
project_idYesThe project ID

Implementation Reference

  • MCP tool handler for 'get_campfire_lines' that calls BasecampClient.getCampfireLines and returns JSON-formatted response.
    case 'get_campfire_lines': {
      const lines = await client.getCampfireLines(typedArgs.project_id, typedArgs.campfire_id);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            status: 'success',
            campfire_lines: lines,
            count: lines.length
          }, null, 2)
        }]
      };
    }
  • src/index.ts:381-392 (registration)
    Tool registration in ListTools response, including name, description, and input schema.
    {
      name: 'get_campfire_lines',
      description: 'Get recent messages from a Basecamp campfire (chat room)',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'The project ID' },
          campfire_id: { type: 'string', description: 'The campfire/chat room ID' },
        },
        required: ['project_id', 'campfire_id'],
      },
    },
  • Input schema definition for the get_campfire_lines tool.
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'The project ID' },
          campfire_id: { type: 'string', description: 'The campfire/chat room ID' },
        },
        required: ['project_id', 'campfire_id'],
      },
    },
  • BasecampClient helper method that performs the actual API call to retrieve campfire lines.
    async getCampfireLines(projectId: string, campfireId: string): Promise<CampfireLine[]> {
      const response = await this.client.get(`/buckets/${projectId}/chats/${campfireId}/lines.json`);
      return response.data;
    }
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-only operation but doesn't specify details like pagination, rate limits, authentication requirements, or what 'recent' means (e.g., time frame or message count). For a tool with zero annotation coverage, this is a significant gap in transparency.

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 purpose without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function, making it highly concise and well-structured.

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 moderate complexity (2 required parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, and output format, which are needed for full completeness. Without annotations or output schema, more guidance would be beneficial.

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 clear descriptions for both parameters in the input schema. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. This meets the baseline for high schema coverage but doesn't enhance 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 verb ('Get') and resource ('recent messages from a Basecamp campfire'), making the tool's purpose immediately understandable. It specifies the scope ('recent messages') and context ('chat room'), though it doesn't explicitly differentiate from sibling tools like 'get_comments' or 'global_search', which prevents 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. It doesn't mention prerequisites, such as needing a valid project and campfire ID, or compare it to similar tools like 'get_comments' or 'search_basecamp'. This leaves the agent without context for tool selection.

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