EZ Lawn Biller by Cotlet

Create customer in EZ Lawn Biller

ez_lawn_biller_create_customer

Read-onlyIdempotent

Create customer 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_create_customer"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description adds behavior beyond the annotations by stating it returns screens/buttons/fields and "opens nothing by itself," reinforcing the readOnlyHint=true annotation and resolving the tension between the "create" name and a read-only tool. It also discloses the handoff to the browser tools, which is valuable operational context not captured by annotations.

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 core purpose and handoff are front-loaded and clear, but the closing sentence about API investigation (404 results, dates, QuickBooks reference) is verbose and tangential padding that does not help an agent invoke the tool.

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 and annotation coverage, the description is largely complete: it says what it returns (step-by-step UI instructions), that it has no side effects, and what to do next. The main gap is the lack of guidance on how it relates to the many sibling customer tools.

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?

There are zero parameters, so the baseline for this dimension is 4; the description has no parameters to explain and does not misrepresent any.

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 names a specific verb and resource ("Create customer in the user's own EZ Lawn Biller account") and then clarifies it returns step-by-step instructions rather than executing the action. It does not differentiate this tool from several close siblings such as ez_lawn_biller_new_customer or ez_lawn_biller_edit_customer, leaving the agent to infer which one applies.

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 implies the workflow — get instructions here, then perform the action with the cotlet_browser_* tools in the Cloud Browser — which is useful sequencing guidance. However, it gives no explicit comparison to the many other customer-creation/edit siblings, so an agent cannot readily tell when this guidance tool is the right choice over those alternatives.

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?