Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_contracts

Retrieve contract data from Simplicate business systems to access agreement details, terms, and associated information for business operations.

Instructions

Retrieve contracts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • Tool registration for 'get_contracts' including input schema definition
      name: 'get_contracts',
      description: 'Retrieve contracts',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number' },
          offset: { type: 'number' },
        },
      },
    },
  • MCP server handler for get_contracts tool call, delegates to SimplicateServiceExtended.getContracts with pagination params
    case 'get_contracts': {
      const data = await this.simplicateService.getContracts({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Core helper method implementing contract retrieval via Simplicate API endpoint /crm/contract, with error handling and pagination
    async getContracts(params?: { limit?: number; offset?: number }): Promise<SimplicateContract[]> {
      try {
        const response = await this.client.get('/crm/contract', params);
        return response.data || [];
      } catch (error) {
        // Contracts endpoint may not be available or requires specific filters
        console.warn('getContracts: endpoint returned error, returning empty array');
        return [];
      }
    }
  • TypeScript interface defining the SimplicateContract return type structure used by getContracts
    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 full burden for behavioral disclosure. 'Retrieve contracts' implies a read operation but provides no information about permissions required, rate limits, pagination behavior (despite having limit/offset parameters), what data is returned, or error conditions. This is inadequate for a tool with parameters.

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 two words. While this represents under-specification rather than ideal conciseness, according to the scoring rules, conciseness evaluates whether every sentence earns its place, and this minimal description has no wasted words. It's front-loaded with the core purpose.

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?

This is a retrieval tool with 2 undocumented parameters, no annotations, and no output schema. The description provides only a tautological statement of purpose with no behavioral context, parameter guidance, or differentiation from sibling tools. For a tool that presumably returns multiple contracts with pagination support, this description is completely inadequate.

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 neither parameter has any documentation in the schema. The description provides no information about the 'limit' and 'offset' parameters - not what they do, their purpose in pagination, acceptable ranges, or default values. The description fails to compensate for the complete 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 'Retrieve contracts' restates the tool name 'get_contracts' in different words, making it tautological. It specifies the verb 'retrieve' and resource 'contracts', but doesn't distinguish this from sibling tools like 'get_contract' (singular) or provide any scope clarification about what contracts are retrieved.

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 about when to use this tool versus alternatives. There's no mention of when to use 'get_contracts' versus 'get_contract' (singular), 'search', or other retrieval tools in the sibling list. No context, prerequisites, or exclusions are stated.

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