Hubstaff MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Hubstaff it covers these actions: List timesheets, Approve timesheet, Review manual time request, Add time entry, Create project, Create task.

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_app_guide"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: Hubstaff.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety bar is low. The description still adds real behavioral context: "Free, no browser session" tells the agent this costs nothing and does not open a Cloud Browser session, and the enumerated contents tell the agent what it gets back. It does not say how large the response is or whether the guidance can go stale.

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?

The trigger sentence is front-loaded, but the opening sentence is a long colon-delimited run-on listing six kinds of content, which is heavier than needed. The trailing Hubstaff action list is concrete and useful but makes the whole thing dense.

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?

With no output schema and both parameters optional, the description must convey what is returned — and it does, itemizing browser choice, sign-in link, method, screens/menus/actions, notes, and dedicated tools, plus concrete Hubstaff action coverage. Only the shape/limits of the returned guidance are left unspecified.

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 description coverage is 100%, so both parameters (app name/slug with Hubstaff default, and task in the user's words) are already documented. The description only implicitly touches the app parameter via the catalog-vs-general-method distinction and never explains how the task string shapes the returned method, so it adds little beyond the schema baseline.

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 states a specific resource — guidance for operating a given web app through Cotlet's browser tools — and enumerates what the guidance contains (which browser, sign-in link, step-by-step method, screens/menus/actions, dedicated tools). It is distinguishable from the cotlet_browser_* siblings, which perform the steps rather than explain them, though it never names cotlet_apps as the catalog sibling it differs from.

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 before the first browser step in an app" gives an explicit trigger point, and "Works for any web app; one outside Cotlet's catalog gets the general method" covers the out-of-catalog case. It does not state a when-not condition or name a concrete alternative, so it stops short of a 5.

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

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