Skip to main content
Glama

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 EZ Lawn Biller it covers these actions: Dashboard, Today's Schedule, Customer search, Setup Wizard, Company settings, Brand colour, Statement contact lines, Held billing reminders, Stripe connection, Gateway Order, Bank transfers, Late Fees, Portal settings, Email settings, SMS settings, Visit Report Settings, Preview, Open web page, Manage Staff, Add Technician, New Staff, Remove staff, Roles & Permissions, Custom role, Staff role, Permission controls, Technician profile, Work Schedule, Staff impersonation, Customer impersonation, Stop Impersonating, Geographic service areas, Technician credentials, Activity log, Customer list, Details, New Customer, Edit customer, Remove customer, Add Location, Service Windows, Billing Address, Phone numbers, CC emails, Customer notes, Pin notes, Customer Settings, Customer delivery settings, Group settings, Undo, Cancel customer, Reactivate customer, Mark on-demand, Service catalog, New recurring item, Edit recurring item, Add service type, Edit service type, Delete service type, Service checklist, Restore default, Inventory checklist, Add Item, New one-time service, Edit one-time service, Delete one-time service, Add starter services, Recurring Billing, Recurring service, Edit recurring billing, Edit billing item, Change visit days, Pause, Scheduled Pause, Resume, Cancel, Reactivate, Reactivate stopped line, Proration, Auto-Pause, Auto-Resume, Correction preview, Apply correction, Undo cancellation, Schedule, Route map, Create a Draft, Return to LIVE, Apply Draft to LIVE, Move stop, Force anyway, Future-week changes, Route Optimizer, Optimize Order, Apply To All Weeks, Copy to Future Weeks, Lock stop, Customize Routes, Save route changes, Open PDF, Download PDF, Day assignment drawer, Reorder stops, Add visit, Edit visit, Cancel this visit, Delete visits, Services, Mark completed, New On-Demand Customer, Sell a service, One-off billing, Use existing customer, Convert to subscriber, Estimates list, Estimate details, New estimate, Edit estimate, Delete draft, Create customer, Preview as customer, Download PDF, Send / Resend, Resend selected, Generate & copy link, Extend validity, Revoke link, Void, Record approval, Bill the customer, Bill now, Schedule jobs, Edit estimate job, Delete estimate job, Templates, New template, Edit template, Archive template, Estimate settings, Billing History, Issue Charge, Record Payment, Issue Credit, Refund, Change charge date, Statements, Statement PDF, Send statement, Email All Statements, Email Selected, Print All, Text All, Statement automation, Send next month's statements, Statement preview, Statement dry run, Statement test, Statement run, Statements to print, Changes after sending, Send updated statement, Mark as reviewed, Review held billing, Bill held periods, Skip held periods, Waive this late fee, Customer late fees, Default autopay method, Payment retries, Confirmation thresholds, Offer PayPal automatic payments again, Past-due recipients, Save notice draft, Notice templates, Notice preview, Notice dry run, Send test to me, Review & send notices, Run history, Retry failed notices, Cancel run, Print notice exceptions, Export notice CSV, Catalog, Inventory item, Stock, Add stock, Transfer stock, Manual adjustment, Activity, Chemical Usage, Chemical Cost, Low-stock alerts, Inventory Value, Material Cost Per Service, Usage Trends, Daily schedule, Service summary, Checklist, Supplies used, Service notes, Sync status, Mobile App Data, Photo evidence, Minimum photo requirements, Problem reports, Customer Dashboard, Billing history, Statements, Payments, Change saved card, Remove saved card, Automatic payments, Cancel automatic payments, Services, Reset portal password, Email portal password, Service visit reports, Compose email, Send email, Compose text, Send text, Message Log, SMS Usage, Appointment reminders, Custom templates, Notification types, Customer preferences, Delivery tracking, Report Access, Visit report subscription, Send visit report, Pay Profile, Technician pay, Run Payroll, Review payroll, Finalize payroll, Pay Statements, Pay statement PDF, Historical payroll, Earnings reports, Per-service rates, Distribute pay statements, Balances, Income, Credits, Charges, Recurring, Lawn Treated, Schedule report, Sales Tax, Inventory report, Report filters, Open schedule PDF, Download schedule PDF, Schedule CSV, Export report, Technician performance, Refund reporting, Connect to QuickBooks, Reconnect, Disconnect QuickBooks, Auto-sync, Export Dashboard, Export customers, Export items, Export statements, Export payments, Retry export, Default Income Account, Manage EZ Lawn Biller Plan, Manual help, Estimate help, Email support, Configure card paypal processing fee, Submit field problem report, Read route efficiency analytics.

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: EZ Lawn Biller.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description does add two genuinely useful behavioral facts beyond that: it is "Free, no browser session" (no browser/credit consumption) and out-of-catalog apps still return the general method rather than failing. It says nothing about response size or whether the returned guide is cached/refreshed, so it stops at a solid 3.

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 first three sentences are well front-loaded and earn their place, but the trailing list of roughly 300 EZ Lawn Biller action names is a massive, unscannable dump that dwarfs the actual guidance. It reads as a keyword index rather than instruction, and an agent gets that content from the tool's return value anyway. This is under-edited, not concise.

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, the description must explain what comes back, and it does: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. For a two-optional-parameter read-only lookup tool that is close to sufficient; only the size/shape of the response is 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 coverage is 100% — both `app` (with default EZ Lawn Biller) and `task` ("in their words") are already documented in the schema. The description reinforces the default implicitly but adds no syntax, format, or mapping guidance linking the `task` string to how the returned method is selected. Baseline 3 is appropriate when the schema does the work.

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 opening states a concrete resource: a guide telling the agent which browser/sign-in link to use, the step-by-step method, the app's screens, menus, actions, notes, and the app's dedicated tools. That distinguishes it from the browser_* action tools, which it explicitly precedes. The purpose is buried under an enormous action enumeration, but it is stated clearly enough to identify.

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 a clear trigger point in the workflow, and "Works for any web app; one outside Cotlet's catalog gets the general method" tells the agent the fallback behavior for unknown apps. There is no explicit when-not or named alternative (e.g. cotlet_apps for catalog lookup), so it falls 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources