Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_absences

Retrieve employee absence records to track time off, sick leave, and other work absences from the Simplicate business management system.

Instructions

Retrieve employee absences

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • The core handler logic for fetching absences from the Simplicate HRM API endpoint '/hrm/absence'. This is the implementation executed when the 'get_absences' tool is called via dynamic dispatching in http-mcp-server.
    async getAbsences(params?: { limit?: number; offset?: number }): Promise<SimplicateAbsence[]> {
      const response = await this.client.get('/hrm/absence', params);
      return response.data || [];
    }
  • Type definition/schema for the absence objects returned by getAbsences
    export interface SimplicateAbsence {
      id: string;
      employee?: { id: string; name: string };
      absence_type: string;
      start_date: string;
      end_date: string;
    }
  • Dynamic tool dispatcher that maps 'get_absences' tool name to 'getAbsences' service method via toMethodName conversion and executes it using SimplicateServiceExtended instance.
    async function dispatchTool(toolName: string, args: any) {
      const method = toMethodName(toolName);
      // heuristic param extraction
      const params: any[] = [];
      if (args && typeof args === 'object') {
        // common id patterns
        const idKeys = ['project_id','organization_id','person_id','task_id','service_id','invoice_id','id'];
        let foundId = false;
        for (const k of idKeys) {
          if (k in args) {
            params.push(args[k]);
            foundId = true;
            break;
          }
        }
        if (args.data) params.push(args.data);
        if (!foundId && params.length === 0) params.push(args);
      } else if (args !== undefined) {
        params.push(args);
      }
    
      // @ts-ignore - dynamic call
      if (typeof (service as any)[method] === 'function') {
        // call and return
        // Some methods expect a single primitive id; spread params
        return await (service as any)[method](...params);
      }
    
      throw new Error(`Unknown tool/method: ${toolName} -> ${method}`);
    }
  • Utility function that converts MCP tool names like 'get_absences' to service method names like 'getAbsences'.
    function toMethodName(toolName: string) {
      // convert snake_case to camelCase: get_projects -> getProjects
      return toolName.split('_').map((p, i) => i === 0 ? p : p[0].toUpperCase() + p.slice(1)).join('');
    }
Behavior2/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' implies a read operation, but the description doesn't address permissions needed, whether it returns all absences or filtered subsets, pagination behavior (despite having limit/offset parameters), or what format the data returns. This leaves significant gaps 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 three words, with zero wasted language. It's front-loaded with the core purpose and contains no unnecessary elaboration, making it efficient for quick scanning.

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?

For a tool with 2 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how parameters affect results, or behavioral characteristics. The minimal description leaves too many open questions for effective tool selection and 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?

With 0% schema description coverage for both parameters (limit and offset), the description provides no information about what these parameters mean or how they affect the retrieval. The description doesn't mention pagination, result limiting, or any parameter usage, failing 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Retrieve employee absences' clearly states the verb (retrieve) and resource (employee absences), establishing the basic purpose. However, it doesn't differentiate from sibling tools like 'get_leave' which might retrieve similar absence/leave data, leaving ambiguity about scope or relationship between these tools.

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. With sibling tools like 'get_leave' and 'search' available, there's no indication whether this retrieves all absences, filtered absences, or serves a specific use case distinct from those other tools.

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