Skip to main content
Glama
Sign In

Paired Plus by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 Paired Plus it covers these actions: List appointments, Create appointment, Reschedule appointment, Create group booking, List waitlist, Set service pricing, Set booking rules, List clients, Add client note, Save color formula, Set client service time, Send client form, List client forms, Manage standing appointment, List inventory, Manage product, Update stock count, Create purchase order, Receive purchase order, Get inventory report, List sales, Checkout sale, Redeem gift card, Sell membership, Sell service series, Redeem rewards, Configure promotion, Get gift card balances, Sell gift card, List marketing audience, Send email campaign, Configure email follow up, Get campaign report, Get sales insights, Charge card on file, Collect booking deposit, Prepare email campaign, Manage service provider, Manage service, Set staff schedule, Manage booking resources, Create client form, Update client form response, Set client tracking fields, Create product kit, List open purchase orders, Close register, Refund sale, Configure service series, Redeem service series, Configure membership rewards, Create payment type, Apply account payment, Configure card and cancellation policy, Store client payment method, Export marketing list, Send text campaign, List conversations, Send text message, Configure darci automation, Configure product purchase reminder, Configure online promotion, Set gift card amounts, Set shipping fees, Publish last minute booking, Add appointment add on, Cancel appointment, Switch calendar provider, Set calendar preferences, Get business reports, Build custom report, Forecast revenue, Get payroll commissions, Lookup hotel guest, Post room charge, Issue room credit, Reconcile pms night audit, Set interface labels, List online services, Book online appointment, List personal appointments, Buy online gift certificate, Buy online retail, Manage user permissions.

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

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Paired Plus.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, but the description adds genuinely new behavior: the call is free, opens no browser session, and works for any web app with a degraded general-method result outside the catalog. It also previews the shape of the returned guidance (method, screens, menus, notes, dedicated tools). It does not say how to apply the returned guide or whether results are cached, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded opening sentences are well ordered, but roughly 85% of the description is a ~90-item, ungrouped dump of Paired Plus actions that reads as catalog exhaust rather than guidance. It is not organized by category and buries the actionable instructions, making the definition far longer than an agent needs.

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?

The tool is a read-only guidance retrieval with no output schema, so the description must convey what comes back — and it does, listing method, screens, menus, actions, notes and dedicated tools. Combined with the timing instruction, an agent has enough to call it correctly; only guidance on how to consume the returned method is absent.

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 (app, task) are already fully documented, including the Paired Plus default. The description adds only marginal meaning beyond that — that the guide adapts to the named app and that the Paired Plus catalog is broad — so the baseline 3 applies.

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 concrete resource (a per-app operating guide) and enumerates its contents: which browser/sign-in link, the step-by-step method, screens/menus/actions, notes, and the app's dedicated tools. That is enough to tell it apart from the individual browser action siblings (cotlet_browser_click, etc.) and from the dedicated paired_plus_* tools, though the opening phrase 'how to work in an app' is slightly awkward rather than a crisp verb+resource statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger ('Call it before the first browser step in an app') and names the alternative path ('the app's dedicated tools when Cotlet has them'), which routes the agent to paired_plus_* tools when one exists. It also handles the fallback case ('one outside Cotlet's catalog gets the general method'), leaving little to inference.

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

All Paired Plus 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