Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_hours

Retrieve timesheet hours data from Simplicate business management system to track and analyze work time records for projects and tasks.

Instructions

Retrieve timesheet hours

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • Handler logic for the 'get_hours' tool call. It invokes the SimplicateService.getHours method with optional limit and offset parameters, then returns the hours data as a JSON-formatted text response.
    case 'get_hours': {
      const hours = await this.simplicateService.getHours({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(hours, null, 2),
          },
        ],
      };
    }
  • Tool registration entry for 'get_hours' in the ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: 'get_hours',
      description: 'Retrieve timesheet hours from Simplicate',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of hour entries to return (default: 10)',
          },
          offset: {
            type: 'number',
            description: 'Number of hour entries to skip (for pagination)',
          },
        },
      },
    },
  • TypeScript interface defining the structure of SimplicateHours objects returned by the getHours service method.
    export interface SimplicateHours {
      id: string;
      employee?: {
        id: string;
        name: string;
      };
      project?: {
        id: string;
        name: string;
      };
      hours: number;
      start_date: string;
      note?: string;
    }
  • Core service method that performs the HTTP GET request to the Simplicate '/hours/hours' API endpoint to retrieve hours data, applying optional pagination parameters.
    async getHours(params?: { limit?: number; offset?: number }): Promise<SimplicateHours[]> {
      const response = await this.client.get('/hours/hours', params);
      return response.data || [];
    }
Behavior2/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. 'Retrieve' implies a read operation, but the description doesn't mention pagination behavior (despite limit/offset parameters), authentication requirements, rate limits, or what the return format looks like. For a tool with parameters and no output schema, this leaves significant behavioral gaps.

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 phrase that gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core purpose without unnecessary elaboration.

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 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain parameter usage, return values, or behavioral constraints. For a retrieval tool with pagination parameters, this leaves the agent guessing about how to properly invoke it and interpret results.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'timesheet hours' but doesn't explain what 'limit' and 'offset' mean in this context (e.g., pagination controls, default values, or constraints). The description adds no parameter-specific information beyond the generic tool purpose, failing to address the coverage 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 'Retrieve timesheet hours' clearly states the verb (retrieve) and resource (timesheet hours), making the purpose immediately understandable. It distinguishes from sibling tools like 'get_hours_entry' or 'get_timesheets' by focusing specifically on timesheet hours rather than entries or timesheets as a whole. However, it doesn't explicitly differentiate from all siblings, keeping it at a 4 rather than a 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. With siblings like 'get_hours_entry', 'get_timesheets', and 'search', there's no indication of whether this is for bulk retrieval, filtered queries, or specific use cases. The agent must infer usage from the name alone, which is insufficient for optimal tool selection.

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