EZ Lawn Biller by Cotlet

Force anyway in EZ Lawn Biller

ez_lawn_biller_force_anyway

Read-onlyIdempotent

Force anyway 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_force_anyway"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with an explicit "opens nothing by itself", which prevents an agent from assuming side effects. The note that no public API exists (404s on /api, /developers, /docs; QuickBooks the only named integration) adds genuine context explaining why browser automation is the path.

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 content is front-loaded and reasonably compact, but the opening sentence is long and run-on, mixing the return format, the no-side-effect guarantee and the handoff to browser tools in one breath. The dated API-discovery note is useful but wordy relative to a zero-parameter lookup tool.

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 output schema, the description helpfully states what the return contains (step-by-step screens, buttons, fields) and which tools to use next, which is what an agent needs operationally. The gap is conceptual: "force anyway" is undefined, so an agent cannot verify that the returned steps match the user's actual intent.

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 no parameter meaning to convey and the baseline is 4. The description adds nothing parameter-related, but nothing is missing either.

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 makes clear what the tool returns (step-by-step screens, buttons and fields for doing "force anyway" in EZ Lawn Biller) and that it performs no action itself. However, the core action "force anyway" is never defined – an agent cannot tell what is being forced or overridden, so the resource-level purpose stays vague despite the clear output shape.

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 gives a usable workflow: call this to get instructions, then execute with the cotlet_browser_* tools in the user's Cloud Browser. That implies when to use it, but there is no guidance on when not to use it or how it relates to the many other ez_lawn_biller_* action tools, leaving the agent to infer selection.

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?