Timetastic MCP Server and API by Cotlet

List wallchart absences in Timetastic

timetastic_list_wallchart_absences

Read-onlyIdempotent

List wallchart absences in the user's own Timetastic account from ChatGPT, Claude or any AI agent. Returns how to do it in Timetastic step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Timetastic Cloud Browser. Timetastic's official API: Yes, Timetastic has a REST API with a bearer token, and no official MCP server (checked 20 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timetastic_list_wallchart_absences"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false. The description adds genuine context beyond them: it opens nothing by itself and returns procedural steps that require a follow-up browser session. It does not describe step format or failure/pagination behavior.

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

Conciseness2/5

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

The useful core is buried in a run-on sentence, and the trailing API/MCP-server availability trivia ('checked 20 Oct 2026') is irrelevant to selection or invocation. That sentence does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The key behavior (returns instructions, performs no action, then hand off to browser tools) is present, which is adequate for a zero-parameter tool. However, with no output schema, more detail on what the steps cover would add value, and vendor API trivia occupies space instead.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4 per rule. The description correctly implies no input is required for this lookup.

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?

States a specific verb and resource ('List wallchart absences') and clarifies the unusual return type: step-by-step Timetastic UI instructions rather than data. It does not explicitly differentiate itself from siblings like timetastic_list_pending_leave_requests.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage flow: call this to get the steps, then execute them with cotlet_browser_* tools in the user's Timetastic Cloud Browser. It does not state when to prefer/avoid alternatives among the sibling leave tools.

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

All Timetastic MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?