Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_person

Retrieve detailed contact information from Simplicate CRM using a person ID to access specific individual records and business data.

Instructions

Get specific person by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idYes

Implementation Reference

  • Registration of the 'get_person' tool in ListToolsRequestHandler, including name, description, and input schema requiring 'person_id'.
    {
      name: 'get_person',
      description: 'Get details of a specific person by ID',
      inputSchema: {
        type: 'object',
        properties: {
          person_id: {
            type: 'string',
            description: 'The ID of the person to retrieve',
          },
        },
        required: ['person_id'],
      },
    },
  • MCP tool handler for 'get_person': validates input, calls SimplicateService.getPersonById, returns JSON response.
    case 'get_person': {
      if (!toolArgs.person_id) {
        throw new Error('person_id is required');
      }
      const person = await this.simplicateService.getPersonById(
        toolArgs.person_id as string
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(person, null, 2),
          },
        ],
      };
    }
  • Core helper function getPersonById that performs API GET request to Simplicate /crm/person/{personId}.
    async getPersonById(personId: string): Promise<SimplicatePerson> {
      const response = await this.client.get(`/crm/person/${personId}`);
      return response.data;
    }
  • TypeScript interface defining the structure of a SimplicatePerson object returned by the tool.
    export interface SimplicatePerson {
      id: string;
      first_name: string;
      family_name: string;
      email?: string;
      phone?: string;
      organization?: {
        id: string;
        name: string;
      };
    }
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 'Get' which implies a read operation, but doesn't clarify if this requires authentication, what happens with invalid IDs (e.g., errors or null returns), or any rate limits. This leaves significant gaps for a tool that likely accesses sensitive person 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 extremely concise with just four words, front-loading the core purpose without any fluff. Every word ('Get', 'specific', 'person', 'ID') contributes directly to understanding the tool's function.

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 tool with no annotations, 0% schema description coverage, and no output schema, the description is inadequate. It doesn't explain what data is returned (e.g., person attributes), error handling, or authentication needs, leaving the agent with insufficient context to use it effectively in a real-world scenario.

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 description mentions 'by ID', which aligns with the single parameter 'person_id' in the schema. However, with 0% schema description coverage, the description doesn't add details like ID format (e.g., numeric vs. string), validation rules, or examples. It provides minimal semantic context beyond what's inferred from the parameter name.

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 ('Get') and resource ('specific person by ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_persons' (plural) or 'get_employee', which suggests it retrieves a single person rather than a list or employee-specific data.

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_persons' for listing multiple people or 'get_employee' for employee-specific data, nor does it specify prerequisites such as needing a valid person ID.

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