Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

create_organization

Create a new organization in Simplicate by providing the organization name and optional contact details like email, phone, and website.

Instructions

Create a new organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
nameYesOrganization name
phoneNo
websiteNo

Implementation Reference

  • Registration of the 'create_organization' tool including its input schema definition.
    {
      name: 'create_organization',
      description: 'Create a new organization',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Organization name' },
          email: { type: 'string' },
          phone: { type: 'string' },
          website: { type: 'string' },
        },
        required: ['name'],
      },
    },
  • MCP server handler for 'create_organization' tool that delegates to SimplicateServiceExtended.createOrganization.
    case 'create_organization': {
      const data = await this.simplicateService.createOrganization(toolArgs);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Core implementation of organization creation via Simplicate API POST to /crm/organization endpoint.
    async createOrganization(data: Partial<SimplicateOrganization>): Promise<SimplicateOrganization> {
      const response = await this.client.post('/crm/organization', data);
      return response.data;
    }
  • TypeScript interface defining the SimplicateOrganization structure used in createOrganization.
    export interface SimplicateOrganization {
      id: string;
      name: string;
      coc_code?: string;
      email?: string;
      phone?: string;
      website?: string;
      relation_type?: string;
      address?: any;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention permissions required, whether it's idempotent, rate limits, or what happens on success/failure, which is inadequate for a mutation tool.

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, front-loaded sentence with zero waste, making it highly concise and well-structured for quick understanding, though it may be overly brief.

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 complexity of a creation tool with 4 parameters, low schema coverage (25%), no annotations, and no output schema, the description is incomplete. It doesn't cover parameter details, behavioral aspects, or expected outcomes, making it insufficient for effective tool 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?

Schema description coverage is low at 25%, with only 'name' parameter documented. The description adds no meaning beyond the schema, failing to explain parameters like 'email', 'phone', or 'website', or their formats/constraints, leaving significant gaps.

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 verb 'Create' and the resource 'organization', making the purpose explicit. It distinguishes from siblings like 'update_organization' by indicating creation rather than modification, but doesn't specify what an organization entails in this context.

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 alternatives like 'update_organization' or 'get_organizations'. The description lacks context about prerequisites, such as permissions or system state, leaving the agent without usage direction.

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