EZ Lawn Biller by Cotlet

Cancel automatic payments in EZ Lawn Biller

ez_lawn_biller_cancel_automatic_payments

Read-onlyIdempotent

Cancel automatic payments 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_automatic_payments"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

The description reinforces the annotations by stating explicitly that the tool "opens nothing by itself" and only returns screens, buttons and fields, which tells the agent no state changes occur despite the word "cancel" in the name. It also discloses the absent official API and the 404 evidence for /api, /developers and /docs, explaining why browser automation is the fallback. It stops short of saying whether the returned steps are static or account-specific.

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 and the follow-up action are front-loaded in the first two sentences, and the API-research note is placed last as justification. That final sentence is long and reads like provenance logging, but it does earn its place by explaining why the cotlet_browser_* route exists.

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 zero-parameter tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields), that no action is taken, and which tools finish the job. What is missing is any mention of prerequisites, such as the user needing an authenticated EZ Lawn Biller session in the Cloud Browser before the follow-up browser calls will work.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing further for the description to disambiguate. The empty schema is consistent with a pure guidance tool that implicitly operates on the caller's own account.

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 pairs a specific verb and resource ("Cancel automatic payments") with an immediate clarification that the tool returns step-by-step instructions rather than executing anything, which resolves the ambiguity the name alone would create. It does not name or differentiate itself from nearby siblings such as ez_lawn_biller_automatic_payments or ez_lawn_biller_cancel, relying instead on the cotlet_browser_* handoff to show its niche.

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?

It gives clear workflow guidance: this tool yields the how-to, and the actual cancellation is then performed with the cotlet_browser_* tools in the user's Cloud Browser. There are no explicit when-not conditions and no named sibling alternatives, so an agent must infer that it should not call other cancel_* tools for the same goal.

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?