Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

get_documents

Retrieve a list of documents from a specific vault by providing the project ID and vault ID, enabling efficient document management within Basecamp MCP Server.

Instructions

List documents in a vault

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
vault_idYesVault ID

Implementation Reference

  • MCP tool handler for 'get_documents' that calls the Basecamp client's getDocuments method and returns a formatted JSON response.
    case 'get_documents': {
      const documents = await client.getDocuments(typedArgs.project_id, typedArgs.vault_id);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            status: 'success',
            documents,
            count: documents.length
          }, null, 2)
        }]
      };
    }
  • src/index.ts:407-418 (registration)
    Registration of the 'get_documents' tool in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'get_documents',
      description: 'List documents in a vault',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'Project ID' },
          vault_id: { type: 'string', description: 'Vault ID' },
        },
        required: ['project_id', 'vault_id'],
      },
    },
  • Input schema definition for the 'get_documents' tool validating project_id and vault_id parameters.
    inputSchema: {
      type: 'object',
      properties: {
        project_id: { type: 'string', description: 'Project ID' },
        vault_id: { type: 'string', description: 'Vault ID' },
      },
      required: ['project_id', 'vault_id'],
    },
  • Core helper method in BasecampClient that performs the API call to retrieve documents from a project vault.
    async getDocuments(projectId: string, vaultId: string): Promise<Document[]> {
      const response = await this.client.get(`/buckets/${projectId}/vaults/${vaultId}/documents.json`);
      return response.data;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('List') without detailing aspects like whether it's read-only, requires authentication, includes pagination, or returns metadata. This leaves significant gaps for a tool that likely interacts with data.

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 is front-loaded and wastes no words. It directly conveys the core purpose without unnecessary elaboration, 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.

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. It does not explain what the tool returns (e.g., list format, document details) or behavioral traits like error handling. For a tool with two required parameters and no structured output info, more context is needed.

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 parameters 'project_id' and 'vault_id' clearly documented. The description adds no additional meaning beyond implying a vault context, so it meets the baseline of 3 where the schema does the heavy lifting.

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 'List documents in a vault' clearly states the action ('List') and resource ('documents in a vault'), making the purpose immediately understandable. However, it does not differentiate from sibling tools like 'get_uploads' or 'trash_document', which might also involve documents, so it lacks 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. For example, it does not mention when to choose 'get_documents' over 'global_search' or 'search_basecamp' for document retrieval, nor does it specify prerequisites like needing a vault context.

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