EZ Lawn Biller by Cotlet

Chemical Usage in EZ Lawn Biller

ez_lawn_biller_chemical_usage

Read-onlyIdempotent

Chemical Usage 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_chemical_usage"
  }
}

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 cover readOnly, idempotent, and non-destructive, so the bar is lower. The description still adds real behavioral context beyond them: it explicitly states it opens nothing by itself, that the output is procedural instructions, and that no public EZ Lawn Biller API exists (404 on /api, /developers, /docs), justifying reliance on browser tools.

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 is front-loaded and the follow-up workflow is clear, but the closing API-availability paragraph is verbose and reads like research notes (including a dated finding) rather than guidance the agent needs at call time. It could be one clause instead of a full sentence with URLs.

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, annotation-covered tool with no output schema, the description covers what is returned (step-by-step screens/buttons/fields), what it does not do (opens nothing), and the intended follow-up (cotlet_browser_* tools). The only gap is the lack of sibling differentiation for related chemical 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the description contradicts the empty schema.

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 eventually reveals that this tool returns step-by-step guidance (screens, buttons, fields) rather than chemical usage data, which is important disambiguation. However, the opening sentence 'Chemical Usage in the user's own EZ Lawn Biller account' frames it as a data resource, and the actual verb/return type is buried mid-sentence. It does not distinguish itself from the sibling ez_lawn_biller_chemical_cost.

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 workflow ('then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser') and states 'opens nothing by itself', which tells the agent this is an instruction-only tool. But it never says when to choose this over chemical_cost or other usage siblings, and there are no explicit exclusions.

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?