Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_organizations

Retrieve CRM organizations from Simplicate business data to access company information and manage customer relationships.

Instructions

Retrieve CRM organizations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • MCP tool handler for 'get_organizations': extracts params, calls simplicateService.getOrganizations(), formats response as JSON text.
    case 'get_organizations': {
      const data = await this.simplicateService.getOrganizations({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
  • Tool registration including name, description, and input schema definition.
    name: 'get_organizations',
    description: 'Retrieve CRM organizations',
    inputSchema: {
      type: 'object',
      properties: {
        limit: { type: 'number' },
        offset: { type: 'number' },
      },
    },
  • TypeScript interface defining the structure of SimplicateOrganization (output type/schema).
    export interface SimplicateOrganization {
      id: string;
      name: string;
      coc_code?: string;
      email?: string;
      phone?: string;
      website?: string;
      relation_type?: string;
      address?: any;
  • Helper method implementing the core API call to fetch organizations from Simplicate CRM endpoint '/crm/organization'.
    async getOrganizations(params?: { limit?: number; offset?: number }): Promise<SimplicateOrganization[]> {
      const response = await this.client.get('/crm/organization', params);
      return response.data || [];
  • Alternative/basic MCP tool handler for 'get_organizations' in server.basic.ts.
    case 'get_organizations': {
      const organizations = await this.simplicateService.getOrganizations({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(organizations, null, 2),
          },
        ],
      };
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 'retrieve' which implies a read-only operation, but doesn't mention pagination behavior (implied by limit/offset parameters), authentication requirements, rate limits, or what the response format looks like. For a list tool with parameters, this leaves significant behavioral gaps.

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 just three words, with zero wasted language. It's front-loaded with the essential action and resource, making it immediately scannable and efficient for an AI agent to parse.

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 a tool with 2 parameters (0% schema coverage), no annotations, no output schema, and multiple sibling tools, the description is inadequate. It doesn't explain parameter usage, return format, pagination behavior, or differentiation from similar tools. For a list operation in a CRM context, this leaves too many gaps for effective tool selection and invocation.

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 description provides no information about the two parameters (limit and offset), and schema description coverage is 0%. While 'retrieve CRM organizations' implies a list operation, it doesn't explain that limit controls result count or offset enables pagination. The description fails to compensate for the complete lack of parameter documentation in the schema.

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 'Retrieve CRM organizations' clearly states the verb (retrieve) and resource (CRM organizations), making the tool's purpose immediately understandable. It distinguishes from siblings like 'get_organization' (singular) by implying a list operation, though it doesn't explicitly contrast with other retrieval tools like 'get_persons' or 'get_projects'.

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 when to choose 'get_organizations' over 'get_organization' (singular), 'search', or other list tools, nor does it specify prerequisites or typical use cases for retrieving organizations in the CRM 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