Timesheet MCP Server

Official

by timesheetIO

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Cancel Absence

absence_cancel

Idempotent

Cancel an absence by providing organization ID, absence ID, and cancellation reason.

Instructions

Cancel an absence with a reason.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>",
      "id": "<id>",
      "reason": "<reason>"
    },
    "name": "absence_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`organizationId`	Yes
`id`	Yes
`reason`	Yes

Output Schema

Name	Required	Description
`id`	No	Resource ID
`success`	No
`deletedId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jun 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already indicate idempotent and non-destructive mutation. Description adds minimal behavioral insight beyond stating the action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise at 5 words, but too terse for a 3-parameter tool. Lacks parameter context.

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?

Despite having an output schema, the description omits necessary context for a cancellation action, such as the difference from deletion and the role of 'reason'.

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 coverage, description only mentions 'reason' and fails to explain organizationId or id, leaving critical parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

Clearly states verb 'cancel' and resource 'absence', with additional detail 'with a reason'. Distinguishes from siblings like absence_delete and absence_reject.

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 on when to use cancel versus delete or reject. Missing prerequisites or context for when cancellation is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.