Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

create_document

Generate and store a document in a specific vault by providing the project ID, vault ID, title, and HTML content using the Basecamp MCP Server tool.

Instructions

Create a document in a vault

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesDocument HTML content
project_idYesProject ID
titleYesDocument title
vault_idYesVault ID

Implementation Reference

  • Core handler function that executes the document creation logic by posting to the Basecamp API.
    async createDocument(
      projectId: string,
      vaultId: string,
      title: string,
      content: string,
      status = 'active'
    ): Promise<Document> {
      const response = await this.client.post(`/buckets/${projectId}/vaults/${vaultId}/documents.json`, {
        title,
        content,
        status,
      });
      return response.data;
    }
  • Input schema for validating tool parameters in MCP tool calls.
    inputSchema: {
      type: 'object',
      properties: {
        project_id: { type: 'string', description: 'Project ID' },
        vault_id: { type: 'string', description: 'Vault ID' },
        title: { type: 'string', description: 'Document title' },
        content: { type: 'string', description: 'Document HTML content' },
      },
      required: ['project_id', 'vault_id', 'title', 'content'],
    },
  • src/index.ts:420-432 (registration)
    Tool object registration in the MCP ListTools handler, defining name, description, and schema.
      name: 'create_document',
      description: 'Create a document in a vault',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'Project ID' },
          vault_id: { type: 'string', description: 'Vault ID' },
          title: { type: 'string', description: 'Document title' },
          content: { type: 'string', description: 'Document HTML content' },
        },
        required: ['project_id', 'vault_id', 'title', 'content'],
      },
    },
  • MCP CallToolRequest dispatch handler for create_document, invoking the client method and formatting the tool response.
    case 'create_document': {
      const document = await client.createDocument(
        typedArgs.project_id,
        typedArgs.vault_id,
        typedArgs.title,
        typedArgs.content
      );
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            status: 'success',
            document
          }, null, 2)
        }]
      };
    }
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 states 'Create a document in a vault,' implying a write/mutation operation, but doesn't cover permissions, side effects, error handling, or response format. This is inadequate for a tool that likely modifies data, leaving significant gaps in understanding its behavior.

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 no wasted words, making it easy to parse and understand quickly. It's appropriately sized for its purpose and front-loaded with the core action.

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 complexity of a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation, potential errors, or how it fits into the broader system with siblings like 'get_documents' or 'trash_document'. This leaves the agent with insufficient context for 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 input schema has 100% description coverage, with each parameter clearly documented (e.g., 'Document HTML content' for 'content'). The description doesn't add any meaning beyond the schema, such as explaining relationships between parameters or usage examples, so it meets the baseline score for high schema 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 ('Create') and resource ('document in a vault'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_card' or 'create_column', which also create resources, so it doesn't reach the highest 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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention when to use 'create_document' instead of 'create_card' or how it relates to 'trash_document' or 'update_document' among the siblings. 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