EZ Lawn Biller by Cotlet

Cancel in EZ Lawn Biller

ez_lawn_biller_cancel

Read-onlyIdempotent

Cancel in the user's own EZ Lawn Biller account from ChatGPT, Claude or any AI agent. Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. EZ Lawn Biller's official API: No publicly documented EZ Lawn Biller API was found on 11 Nov 2026: ezlawnbiller.com/api, /developers and /docs returned 404, and its FAQ and manual name QuickBooks as the only integration.

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": "ez_lawn_biller_cancel"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly and non-destructive; the description adds real value beyond them by stating it opens nothing by itself and describing the return format as ordered steps with screens, buttons and fields. The API-availability note explains why a browser path is needed instead of an API call.

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

Conciseness4/5

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

The core behavior is front-loaded in the first two sentences, which is what an agent needs. The closing API-documentation sentence is longer than necessary but does explain the absence of a direct integration route.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by describing the returned step-by-step instructions, so return-value knowledge is adequate. The remaining gap is scope: which cancellation target this tool covers relative to the many specific cancel_* siblings is left unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is no per-parameter meaning to add and the schema is trivially complete. The description says nothing misleading about inputs and notes that the following browser step needs the user's own cloud browser session.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb (cancel) and the surface (the user's own EZ Lawn Biller account) but never says what is being cancelled, so with siblings like ez_lawn_biller_cancel_customer, _cancel_run, _cancel_this_visit and _cancel_automatic_payments an agent cannot tell what this generic entry covers. It does clarify the deliverable (step-by-step screens, buttons, fields) rather than an execution, which is genuinely distinguishing.

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

Usage Guidelines3/5

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

It says to run this first and then perform the action with the cotlet_browser_* tools, which implies a use-then-act workflow. It gives no explicit exclusions or routing to the entity-specific cancel_* siblings, so guidance is implied rather than stated.

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