Skip to main content
Glama
Sign In

Shiftbase MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Open the browser

cotlet_browser_open
Read-only

Starts the user's Cloud Browser (a real Chrome on Cotlet, where the user is signed in to their sites) and opens url. Call it first. The URL goes to the site's open tab, else to a new tab, so the user's own tabs stay. Answers the page after it: the elements and text in view, with the same numbers. In Shiftbase it serves these actions: List timesheet entries, Approve timesheet entries, Approve absence request, Decline absence request, Approve exchange request, List open shifts, List shifts, Add worked hours.

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": "cotlet_browser_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
urlNoA public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the browser is a signed-in real Chrome, the URL reuses the site's open tab before opening a new one, the user's own tabs are preserved, and the call returns the page's visible elements and text. That last point matters because there is no output schema. Missing are failure modes such as what happens if the browser cannot start or the URL is unreachable.

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?

Front-loads the action and the 'call it first' rule before the behavioral detail, and most sentences carry distinct information. The trailing enumeration of eight Shiftbase actions is long and partly redundant with the sibling `shiftbase_*` tool names, which dilutes the otherwise tight prose.

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 two-parameter, fully documentedschema tool with no output schema, the description covers what it does, when to call it, how the URL is routed, and what the agent receives back (visible elements and text). Nothing essential for a correct first call is missing.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, including `app`'s 'leave it out' guidance and the slug pattern. The description adds the routing semantics of `url` (existing site tab first, otherwise a new tab), which is genuine added meaning, but never touches `app`.

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: starts the user's Cloud Browser (real Chrome on Cotlet) and opens `url`. 'Call it first' implies the ordering versus the many `cotlet_browser_*` siblings, but it never names `navigate` or another sibling to draw the boundary explicitly.

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?

'Call it first' gives a concrete sequencing rule for the browser tool family, and the Shiftbase action list tells the agent which tasks chain through this tool. It stops short of stating when not to use it (e.g. when a session already exists or when the target is already the active tab), so no true exclusion is given.

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 toolsInspect
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