Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

create_contract

Generate new contracts in Simplicate by specifying organization details and contract dates to establish business agreements.

Instructions

Create a new contract

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNo
organization_idYes
start_dateYes

Implementation Reference

  • Tool registration including name, description, and input schema for 'create_contract' in the ListTools handler.
    {
      name: 'create_contract',
      description: 'Create a new contract',
      inputSchema: {
        type: 'object',
        properties: {
          organization_id: { type: 'string' },
          start_date: { type: 'string' },
          end_date: { type: 'string' },
        },
        required: ['organization_id', 'start_date'],
      },
    },
  • MCP tool handler for 'create_contract' that delegates to SimplicateServiceExtended.createContract and formats response.
    case 'create_contract': {
      const data = await this.simplicateService.createContract(toolArgs);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Core implementation of createContract method that performs HTTP POST to Simplicate API endpoint '/crm/contract'.
    async createContract(data: Partial<SimplicateContract>): Promise<SimplicateContract> {
      const response = await this.client.post('/crm/contract', data);
      return response.data;
    }
  • TypeScript interface defining the SimplicateContract data structure used by createContract.
    export interface SimplicateContract {
      id: string;
      contract_number: string;
      organization?: { id: string; name: string };
      start_date: string;
      end_date?: string;
      status: string;
    }
Behavior1/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 only states 'Create a new contract' without mentioning permissions required, side effects, error handling, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 three words, with no wasted language. It is front-loaded and to the point, though this brevity contributes to its inadequacy in other dimensions.

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 complexity of creating a contract, no annotations, no output schema, and 0% schema coverage, the description is severely incomplete. It fails to provide necessary context on behavior, parameters, or 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.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the three parameters (end_date, organization_id, start_date) are documented in the schema. The description adds no information about these parameters, failing to compensate for the lack of schema documentation.

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 'Create a new contract' restates the tool name with minimal elaboration, making it tautological. It specifies the verb 'create' and resource 'contract' but lacks detail on what a contract entails or how it differs from sibling tools like create_quote or create_invoice, leaving the purpose vague 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?

No guidance is provided on when to use this tool versus alternatives. With siblings like create_quote and create_invoice, there's no indication of prerequisites, context, or exclusions, leaving the agent without direction on appropriate usage scenarios.

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