Shiftbase MCP Server and API by Cotlet

Approve timesheet entries in Shiftbase

shiftbase_approve_timesheet_entries

Read-onlyIdempotent

Approve timesheet entries in the user's own Shiftbase account from ChatGPT, Claude or any AI agent. Returns how to do it in Shiftbase step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Shiftbase Cloud Browser. Shiftbase's official API: Shiftbase has a Public API for employees, schedules, time registration, clocks and reports, but no official MCP server (checked 22 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": "shiftbase_approve_timesheet_entries"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint, idempotentHint, and destructiveHint annotations, it states that the tool opens nothing by itself, returns step-by-step guidance, and requires follow-up browser tools. It does not describe auth requirements or rate limits, but the side-effect behavior is clear.

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 core behavior is front-loaded in the first two sentences, and the third explains the official API/MCP context. There is some filler ('from ChatGPT, Claude or any AI agent') and a dated verification note, but the description remains compact.

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

Completeness5/5

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

For a zero-parameter, read-only guide tool with no output schema, the description covers what is returned (screens, buttons, fields), that nothing is opened, and which tools to use next. That is enough for an agent to invoke it correctly.

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?

The tool has zero parameters, so the baseline is 4; there are no parameter semantics for the description to add, and the empty schema is consistent with a generic how-to guide.

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 names the resource (timesheet entries), the account scope (the user's own Shiftbase account), and clarifies that the tool returns step-by-step instructions rather than performing the approval. That clarification prevents the name's 'approve' verb from being misleading, though the initial verb still implies action before the second sentence corrects it.

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?

It explicitly says to use this tool to obtain screens/buttons/fields and then use the cotlet_browser_* tools in the Shiftbase Cloud Browser. It does not enumerate when not to use it or name specific browser siblings, but the sequencing is clear.

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

All Shiftbase 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?