Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_persons

Retrieve contact persons from Simplicate business data to access CRM information, manage contacts, and support customer relationship management activities.

Instructions

Retrieve contact persons

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • Registration of the 'get_persons' tool in the ListToolsRequestHandler, including name, description, and input schema.
    {
      name: 'get_persons',
      description: 'Retrieve a list of persons (contacts) from Simplicate',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of persons to return (default: 10)',
          },
          offset: {
            type: 'number',
            description: 'Number of persons to skip (for pagination)',
          },
        },
      },
    },
  • Tool handler for 'get_persons' in CallToolRequestHandler switch statement. Extracts parameters, calls SimplicateService.getPersons, and returns JSON-formatted response.
    case 'get_persons': {
      const persons = await this.simplicateService.getPersons({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(persons, null, 2),
          },
        ],
      };
    }
  • Core helper function implementing getPersons logic by calling the Simplicate API endpoint '/crm/person' with optional pagination parameters.
    async getPersons(params?: { limit?: number; offset?: number }): Promise<SimplicatePerson[]> {
      const response = await this.client.get('/crm/person', params);
      return response.data || [];
    }
  • TypeScript interface defining the structure of a SimplicatePerson (output schema for getPersons).
    export interface SimplicatePerson {
      id: string;
      first_name: string;
      family_name: string;
      email?: string;
      phone?: string;
      organization?: {
        id: string;
        name: string;
      };
    }
  • Alternative handler for 'get_persons' in the full-featured MCP server using SimplicateServiceExtended.
    case 'get_persons': {
      const data = await this.simplicateService.getPersons({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
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. 'Retrieve' implies a read-only operation, but the description doesn't specify whether this tool lists all persons, requires authentication, has pagination behavior (implied by limit/offset parameters but not stated), or returns structured data. For a tool with parameters and no annotations, 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 extremely concise at two words ('Retrieve contact persons'), with no wasted language. It's front-loaded with the core action and resource, making it easy to parse quickly. This brevity is appropriate for a simple-sounding tool, though it may sacrifice completeness.

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 tool's complexity (2 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what 'contact persons' entails (e.g., fields returned, data source), how parameters affect retrieval, or the expected output format. For a retrieval tool with pagination parameters, this lack of context makes it inadequate for reliable agent use.

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?

The input schema has 2 parameters (limit, offset) with 0% description coverage, meaning the schema provides no semantic context. The description doesn't mention these parameters at all, failing to compensate for the schema's lack of documentation. This leaves the agent guessing about the purpose and usage of limit and offset, which are critical for pagination.

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 'Retrieve contact persons' clearly states the verb ('retrieve') and resource ('contact persons'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_person' (singular vs. plural), leaving ambiguity about whether this retrieves a single person or multiple persons. The description is specific enough to avoid being a tautology but lacks sibling differentiation.

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 sibling tools like 'get_person' (for single persons) or 'search' (for filtered queries), nor does it specify prerequisites or contexts for usage. This leaves the agent with insufficient information to choose between similar 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

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