Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_contract

Retrieve specific contract details by providing the contract ID to access business agreement information from the Simplicate system.

Instructions

Get specific contract by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contract_idYes

Implementation Reference

  • MCP tool handler for 'get_contract': validates contract_id input and delegates to SimplicateServiceExtended.getContractById
    case 'get_contract': {
      if (!toolArgs.contract_id) throw new Error('contract_id is required');
      const data = await this.simplicateService.getContractById(toolArgs.contract_id);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Tool registration in ListTools handler: defines name, description, and input schema
      name: 'get_contract',
      description: 'Get specific contract by ID',
      inputSchema: {
        type: 'object',
        properties: { contract_id: { type: 'string' } },
        required: ['contract_id'],
      },
    },
  • Input schema definition for get_contract tool
      type: 'object',
      properties: { contract_id: { type: 'string' } },
      required: ['contract_id'],
    },
  • Helper method in SimplicateServiceExtended that performs the actual API call to retrieve contract by ID
    async getContractById(contractId: string): Promise<SimplicateContract> {
      const response = await this.client.get(`/crm/contract/${contractId}`);
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Get') but doesn't clarify whether this is a read-only operation, what permissions are required, error handling (e.g., for invalid IDs), or response format. The description is minimal and fails to address key behavioral aspects beyond the basic action.

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, efficient sentence with no wasted words. It front-loads the core action and resource, making it easy to parse. Every word contributes directly to the tool's purpose, exemplifying ideal conciseness.

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's simplicity (1 parameter, no output schema), the description is incomplete. It lacks behavioral details (e.g., read-only nature, error cases), parameter specifics, and usage context. While minimalism might suffice for very basic tools, this leaves gaps that could hinder correct agent invocation.

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 input schema has 0% description coverage, so the description must compensate. It mentions 'by ID', which implies the 'contract_id' parameter, but doesn't explain the ID format, source, or constraints. With one undocumented parameter, the description adds minimal semantic value, insufficient to bridge the schema gap.

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 'Get specific contract by ID' clearly states the verb ('Get') and resource ('contract'), and specifies the lookup mechanism ('by ID'). It distinguishes from sibling tools like 'get_contracts' (plural) by indicating retrieval of a single contract. However, it doesn't explicitly differentiate from other 'get_' tools that might also retrieve by ID, keeping it at 4 rather than 5.

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. It doesn't mention sibling tools like 'get_contracts' for listing multiple contracts or 'search' for broader queries, nor does it specify prerequisites such as needing a valid contract ID. This lack of contextual direction limits its utility for an AI agent.

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