Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

search

Find projects, organizations, and people in Simplicate business data using natural language queries to access CRM, projects, and contact information.

Instructions

Search across Simplicate resources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
typeNo

Implementation Reference

  • Registration of the 'search' MCP tool including its input schema definition.
    {
      name: 'search',
      description: 'Search across Simplicate resources',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'The search query',
          },
          type: {
            type: 'string',
            description: 'The type of resource to search (project, organization, person)',
            enum: ['project', 'organization', 'person'],
          },
        },
        required: ['query'],
      },
    },
  • MCP tool handler for 'search' that validates input, calls SimplicateService.search, and returns JSON-formatted results.
    case 'search': {
      if (!toolArgs.query) {
        throw new Error('query is required');
      }
      const results = await this.simplicateService.search(
        toolArgs.query as string,
        toolArgs.type as 'project' | 'organization' | 'person' | undefined
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(results, null, 2),
          },
        ],
      };
    }
  • Core search implementation in SimplicateService that constructs the search endpoint and queries the Simplicate API.
    // Search across resources
    async search(query: string, type?: 'project' | 'organization' | 'person'): Promise<any[]> {
      const endpoint = type ? `/search/${type}` : '/search';
      const response = await this.client.get(endpoint, { q: query });
      return response.data || [];
    }
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It doesn't disclose if this is a read-only operation, how results are returned (e.g., pagination, sorting), authentication needs, rate limits, or error handling. 'Search across' hints at a query-based retrieval, but lacks operational details.

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 appropriately sized for a basic tool and front-loaded with the core action, though its brevity contributes to gaps in other dimensions.

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 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain parameter usage, return values, or behavioral traits, making it inadequate for an agent to use this tool effectively without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter semantics. It doesn't explain the 'query' parameter's format or the 'type' enum's purpose (project, organization, person). Without this, the agent lacks context on how to construct effective searches.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search across Simplicate resources' states the verb (search) and target (Simplicate resources), but is vague about scope and specificity. It doesn't distinguish this search tool from potential filtering capabilities in sibling tools like get_projects or get_organizations, nor does it specify what 'resources' encompasses beyond the type parameter's enum values.

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 the many get_* sibling tools (e.g., get_projects, get_organizations). The description implies a cross-resource search, but it doesn't clarify if this is for broad queries or when specific resource retrieval is preferred, leaving the agent without usage 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

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/daanno/simplicate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server