Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_organization

Retrieve detailed information about a specific organization from Simplicate using its unique identifier to access CRM data, contact details, and project information.

Instructions

Get specific organization by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYes

Implementation Reference

  • MCP tool handler for 'get_organization': validates input, calls SimplicateService.getOrganizationById, and returns JSON response.
    case 'get_organization': {
      if (!toolArgs.organization_id) {
        throw new Error('organization_id is required');
      }
      const organization = await this.simplicateService.getOrganizationById(
        toolArgs.organization_id as string
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(organization, null, 2),
          },
        ],
      };
    }
  • Tool registration including name, description, and input schema requiring 'organization_id'.
    {
      name: 'get_organization',
      description: 'Get details of a specific organization by ID',
      inputSchema: {
        type: 'object',
        properties: {
          organization_id: {
            type: 'string',
            description: 'The ID of the organization to retrieve',
          },
        },
        required: ['organization_id'],
      },
    },
  • Core implementation fetches organization data from Simplicate API endpoint `/crm/organization/{id}`.
    async getOrganizationById(organizationId: string): Promise<SimplicateOrganization> {
      const response = await this.client.get(`/crm/organization/${organizationId}`);
      return response.data;
    }
  • TypeScript interface defining the structure of an organization object.
    export interface SimplicateOrganization {
      id: string;
      name: string;
      coc_code?: string;
      email?: string;
      phone?: string;
      website?: string;
      relation_type?: string;
    }
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. It states 'Get' which implies a read operation, but doesn't specify if it's safe, requires authentication, has rate limits, or what happens on invalid input. For a tool with zero annotation coverage, 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 with a single sentence that directly states the tool's function. It is front-loaded and wastes no words, making it easy to parse quickly.

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 has no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't address behavioral aspects, return values, or parameter details, leaving the agent with insufficient information for reliable use in a complex environment.

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 schema description coverage is 0%, and the description only mentions 'by ID' without explaining what the 'organization_id' parameter represents (e.g., format, source, or constraints). It adds minimal meaning beyond the bare schema, failing to compensate for the low coverage.

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 ('Get') and resource ('specific organization by ID'), making the purpose understandable. However, it doesn't explicitly differentiate from its sibling 'get_organizations' (plural), which likely retrieves multiple organizations, so it misses full sibling distinction.

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 like 'get_organizations' or 'update_organization'. It lacks context about prerequisites, such as needing a valid organization ID, or exclusions, leaving the agent with minimal 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