Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

global_search

Search across all Basecamp projects, todos, and campfire messages instantly to find relevant information quickly using a single query.

Instructions

Search projects, todos and campfire messages across all projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

Implementation Reference

  • src/index.ts:139-149 (registration)
    Registration of the 'global_search' MCP tool, including its input schema definition and description. Note: No handler implementation found in the codebase.
    {
  name: 'global_search',
  description: 'Search projects, todos and campfire messages across all projects',
  inputSchema: {
    type: 'object',
    properties: {
      query: { type: 'string', description: 'Search query' },
    },
    required: ['query'],
  },
},
  • src/index.ts:142-148 (schema)
    Input schema for the 'global_search' tool: requires a 'query' string.
    inputSchema: {
  type: 'object',
  properties: {
    query: { type: 'string', description: 'Search query' },
  },
  required: ['query'],
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool searches but doesn't describe how results are returned (format, pagination, sorting), what happens with no matches, or any limitations (rate limits, permissions needed). This leaves significant gaps for a search operation.

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 gets straight to the point with no wasted words. It's appropriately sized for a simple search tool and front-loads the essential information.

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?

For a search tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the return format looks like (e.g., structured results vs raw text), how to interpret results, or any behavioral nuances. Given the complexity of searching across multiple resource types, 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 schema description coverage is 100%, so the schema already documents the single 'query' parameter adequately. The description doesn't add any meaningful semantic context beyond what's in the schema (e.g., search syntax, examples, or special operators), so it meets the baseline 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 action ('Search') and resources ('projects, todos and campfire messages'), making the purpose immediately understandable. However, it doesn't distinguish this from the sibling 'search_basecamp' tool, which appears to serve a similar function, preventing 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 like 'search_basecamp' or other get_* tools. It mentions 'across all projects' which hints at scope but doesn't explicitly state when this is preferred over more specific search or retrieval tools.

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