Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_documents

Retrieve documents from Simplicate business data to access CRM records, project files, timesheets, and invoices for comprehensive business information management.

Instructions

Retrieve documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • Core implementation of getDocuments: fetches documents from Simplicate API endpoint '/documents/document' with optional pagination parameters.
    async getDocuments(params?: { limit?: number; offset?: number }): Promise<SimplicateDocument[]> {
      const response = await this.client.get('/documents/document', params);
      return response.data || [];
    }
  • MCP ServerFull tool dispatch handler for 'get_documents': processes tool arguments, calls service, formats MCP response.
    case 'get_documents': {
      const data = await this.simplicateService.getDocuments({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Tool registration entry in ListToolsRequestHandler: defines name, description, and input schema.
    {
      name: 'get_documents',
      description: 'Retrieve documents',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number' },
          offset: { type: 'number' },
        },
      },
    },
  • TypeScript interface defining the structure of SimplicateDocument objects returned by getDocuments.
    export interface SimplicateDocument {
      id: string;
      title: string;
      description?: string;
      document_type: string;
      created_at: string;
      url?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Retrieve documents' implies a read-only operation, but it fails to specify critical details such as authentication requirements, rate limits, pagination behavior (hinted by 'limit' and 'offset' parameters but not explained), or what happens on errors. This leaves significant gaps in understanding the tool's behavior.

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 two words, which is efficient and front-loaded. However, it borders on under-specification rather than optimal brevity, as it sacrifices necessary detail for conciseness. It earns a high score for structure but loses points for being too minimal to be fully helpful.

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 complexity of a retrieval tool with 2 undocumented parameters, no annotations, and no output schema, the description is incomplete. It does not explain what 'documents' entails, how results are returned, or handle the parameter semantics. This leaves the agent with insufficient information to use the tool effectively in context with its siblings.

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 2 parameters ('limit' and 'offset') with 0% description coverage, meaning their purposes are undocumented. The description 'Retrieve documents' does not mention these parameters at all, failing to add any semantic meaning beyond the schema. This is inadequate given the low schema coverage, as the agent cannot infer how to use these parameters correctly.

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 documents' restates the tool name 'get_documents' with minimal elaboration, making it tautological. It lacks specificity about what 'documents' refers to (e.g., project documents, invoices, contracts) or how it differs from sibling tools like 'get_document' (singular), which suggests a broader retrieval operation but without clear 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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not clarify if this is for listing all documents versus specific ones, or how it relates to sibling tools like 'get_document' (singular) or 'search'. The absence of context leaves 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