EZ Lawn Biller by Cotlet

Charges in EZ Lawn Biller

ez_lawn_biller_charges

Read-onlyIdempotent

Charges 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_charges"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.6/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, but the description still adds meaningful behavior: the tool "opens nothing by itself" and returns step-by-step screens/buttons/fields rather than performing the action. The note that no public EZ Lawn Biller API exists explains why a UI-guide tool is necessary at all, which is context the annotations cannot convey.

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?

Two sentences with a compact structure: the first states output and non-action, the second names the handoff tools. The final API-availability note is longer than strictly needed but earns its place by justifying the tool's existence; the semicolon-joined middle clause is slightly awkward but readable.

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, read-only guidance tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields), what is not done (nothing is opened), and what to do next (cotlet_browser_* tools). The main residual gap is not stating whether the guidance is scoped to viewing versus editing charges.

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 the baseline is 4; there is no parameter meaning the description needs to compensate for. Nothing in the description misrepresents the empty input object.

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?

"Charges in the user's own EZ Lawn Biller account" names a resource but not a verb; the actual behavior only emerges in the second sentence ("Returns how to do it in EZ Lawn Biller step by step"), revealing this is a procedural-guidance tool rather than a data-retrieval one. An agent must read the whole description to learn this, and "Charges" as a topic remains under-specified given the many charge-adjacent siblings.

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?

The description gives a clear follow-on workflow: this tool returns instructions, then the agent should act with the cotlet_browser_* tools in the Cloud Browser. It does not explain when to prefer this over other ez_lawn_biller_* topic tools, nor does it state prerequisites (e.g., whether the Cloud Browser must already be connected).

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?