EZ Lawn Biller by Cotlet

Resume in EZ Lawn Biller

ez_lawn_biller_resume

Read-onlyIdempotent

Resume 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_resume"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description reinforces the annotations ('opens nothing by itself'), which is consistent with readOnlyHint=true and destructiveHint=false, and tells the agent the return is procedural steps. Beyond that it discloses nothing about rate limits, required session/account state, or what happens if no browser session exists; the API-research paragraph adds no behavioral information.

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

Conciseness3/5

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

The first sentence pair is front-loaded and useful, but the closing paragraph about 404s on ezlawnbiller.com/api and QuickBooks being the only integration is tangential justification text that does not help an agent invoke the tool, and the dated reference ('11 Nov 2026') is distracting.

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?

With no parameters and no output schema, the description does need to convey what comes back and what to do next, and it does both (step-by-step screens/buttons/fields, then cotlet_browser_* tools). What is missing is the prerequisite state (an existing authenticated Cloud Browser session) and any routing versus the similarly named auto_resume sibling.

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 zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not wrongly imply any inputs.

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 says it 'Resume[s] in the user's own EZ Lawn Biller account' and returns step-by-step instructions (screens, buttons, fields) rather than acting. That is more than a restatement of the title, but 'resume' is ambiguous (resuming work in a browser session vs. reactivating something) and the later sentence about browser tools and API research muddies the core purpose.

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 states the follow-on path clearly: this tool only returns instructions and you then act with cotlet_browser_* tools in the user's Cloud Browser. However, it gives no when-not-to-use guidance and does not distinguish itself from the sibling ez_lawn_biller_auto_resume, which an agent would need to choose between.

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?