Squire 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 Squire it covers these actions: List appointments, Book appointment, Reschedule appointment, Cancel appointment, List waitlist, Block time off, List clients, Get revenue report.

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: Squire.
`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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered; the description adds the useful cost/side-effect fact 'Free, no browser session,' which tells the agent this call does not touch the live browser. It also discloses the shape of the returned guidance (which browser, sign-in link, method, screens, dedicated tools), going beyond what the annotations say.

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 guidance content is front-loaded and the when-to-call rule is short, but the first sentence is a long run-on inventory and the closing enumeration of eight Squire actions largely duplicates information already available from the squire_* sibling tool names. That trailing list adds bulk without adding much selection value.

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?

There is no output schema, so the description must characterize the return value, and it does: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tool availability. Combined with two trivially simple optional parameters, an agent has enough to call this correctly before its first browser step in an app.

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%, and both optional parameters (app, task) are fully described there, including the default of Squire. The description adds only marginal semantics, mainly that an app outside the catalog falls back to the general method, which clarifies the 'app' parameter's tolerance rather than its format. Baseline 3 is appropriate.

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 (a how-to guide for working in a web app via Cotlet's Cloud Browser tools) and enumerates what it covers: browser selection, sign-in link, the step-by-step method, screens/menus/actions, notes, and the app's dedicated tools. That distinguishes it from the browser action siblings (navigate/click/read) and points at the squire_* tools, though the opening phrase 'How to work in an app' is a bit abstract until the enumeration lands.

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' is an explicit trigger, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets scope. It signals that dedicated tools exist for catalog apps but never states outright that those tools should be preferred over raw browser steps, so the routing rule is implied rather than spelled out.

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

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