Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

update_organization

Modify organization details in Simplicate by providing the organization ID and updated data fields to maintain current business information.

Instructions

Update an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
organization_idYes

Implementation Reference

  • Tool registration including name, description, and input schema definition for update_organization
    {
      name: 'update_organization',
      description: 'Update an organization',
      inputSchema: {
        type: 'object',
        properties: {
          organization_id: { type: 'string' },
          data: { type: 'object' },
        },
        required: ['organization_id', 'data'],
      },
    },
  • MCP CallToolRequest handler switch case that validates input and delegates to SimplicateServiceExtended.updateOrganization
    case 'update_organization': {
      if (!toolArgs.organization_id || !toolArgs.data) throw new Error('organization_id and data required');
      const data = await this.simplicateService.updateOrganization(toolArgs.organization_id, toolArgs.data);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
  • TypeScript interface defining the SimplicateOrganization data structure used for update operations
    export interface SimplicateOrganization {
      id: string;
      name: string;
      coc_code?: string;
      email?: string;
      phone?: string;
      website?: string;
      relation_type?: string;
      address?: any;
    }
  • Core service method implementing the organization update via PUT request to Simplicate API
    async updateOrganization(organizationId: string, data: Partial<SimplicateOrganization>): Promise<SimplicateOrganization> {
      const response = await this.client.put(`/crm/organization/${organizationId}`, data);
      return response.data;
    }
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. 'Update an organization' implies a mutation operation, but it fails to describe critical behaviors such as required permissions, whether changes are reversible, rate limits, error conditions, or what the tool returns. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with just three words, making it front-loaded and free of unnecessary verbiage. However, this brevity borders on under-specification, as it sacrifices clarity for conciseness. While efficient, it lacks the detail needed for effective tool use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (mutation operation with nested objects), lack of annotations, 0% schema description coverage, and no output schema, the description is severely incomplete. It does not address behavioral traits, parameter meanings, usage context, or return values, leaving an agent with insufficient information to use the tool correctly in a real-world scenario.

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%, meaning parameters 'organization_id' and 'data' are undocumented in the schema. The description adds no semantic information about these parameters—it does not explain what 'organization_id' refers to, what fields 'data' can contain, or examples of valid inputs. With two required parameters and no schema descriptions, the description fails to compensate for this lack of coverage.

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

Purpose2/5

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

The description 'Update an organization' is a tautology that merely restates the tool name 'update_organization' without adding any meaningful clarification. It specifies the verb 'update' and resource 'organization' but lacks detail on what aspects can be updated or how it differs from sibling tools like 'create_organization' or 'get_organization'. This minimal restatement provides no additional insight beyond the obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 does not mention prerequisites (e.g., needing an existing organization), exclusions, or comparisons to sibling tools such as 'create_organization' for new organizations or 'get_organization' for retrieval. Without any usage context, an agent cannot determine appropriate scenarios for invocation.

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