Shiftbase MCP Server and API by Cotlet

Decline absence request in Shiftbase

shiftbase_decline_absence_request

Read-onlyIdempotent

Decline absence request 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_decline_absence_request"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the agent knows this tool only returns guidance. The description adds valuable context — 'opens nothing by itself' and the API/MCP availability note — which reinforces non-mutating behavior beyond annotations. It does not describe the format of returned steps or permission-failure behavior.

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?

Front-loaded with the purpose, but the sentence packs multiple ideas and the trailing API parenthetical ('checked 22 Oct 2026') is tangential to selecting or invoking this tool, costing efficiency.

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

Completeness4/5

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

A no-param, no-output-schema tool; the description covers what it returns (step-by-step screens/buttons/fields), that it does nothing on its own, and how to complete the action with browser tools. Lacking only edge-case behavior such as invalid or already-resolved requests.

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 baseline is 4; the description correctly implies the tool needs no input and instead points to the browser workflow for execution, which adds useful interpretive context.

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+resource (decline absence request) and constrains scope to the user's own Shiftbase account. It is distinguishable from shiftbase_approve_absence_request by the verb, though it does not explicitly name the approve sibling as the counterpart.

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 context: it returns step-by-step instructions rather than acting, and instructs the agent to perform the action with cotlet_browser_* tools in the Shiftbase Cloud Browser. It does not state when-not to use or prerequisites.

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?