Skip to main content
Glama
Sign In

EZ Lawn Biller 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 EZ Lawn Biller it serves 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_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

A3.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-idempotent, non-destructive), the description discloses what the browser actually is (a real Chrome where the user is already signed in) and how the URL is routed: into the site's existing tab, otherwise a new tab, so the user's own tabs are preserved. It also previews the response ('the elements and text in view, with the same numbers'), which is exactly the context an agent needs to chain the next step.

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 opening sentences are well front-loaded and efficient, but they are followed by an enormous keyword dump of roughly three hundred EZ Lawn Biller UI action names. That list does not help an agent select or invoke this tool, is not structured for retrieval, and dominates the description's length, so it fails the 'every sentence earns its place' test.

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?

For a two-parameter, annotation-covered launcher with no output schema, the description covers the essentials: what starts, where the URL lands, ordering relative to other tools, and what comes back. What is missing is lifecycle context such as session persistence or when to call `cotlet_browser_close`, but that is a minor gap rather than a blocking one.

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 the schema itself explains the optional `app` slug in detail, so the baseline of 3 applies. The description adds only destination behavior for `url` (existing tab vs. new tab) and says nothing about the `app` parameter, so it does not materially enrich parameter meaning beyond the schema.

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 first sentence gives a specific verb and resource: it starts the user's Cloud Browser (a real, signed-in Chrome) and opens `url`. That is far more concrete than the name alone and lets an agent picture the effect. It does not explicitly distinguish itself from the sibling `cotlet_browser_navigate`, leaving the open-vs-navigate boundary to be inferred from 'Call it first'.

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' is an explicit sequencing instruction that tells the agent when to reach for this tool relative to the other browser tools. There is no explicit when-not guidance (for example, what to do if a browser session is already open, or when `cotlet_browser_navigate` is the right choice instead), so it stops short of full routing guidance.

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

All EZ Lawn Biller 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