EZ Lawn Biller by Cotlet

Gateway Order in EZ Lawn Biller

ez_lawn_biller_gateway_order

Read-onlyIdempotent

Gateway Order 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_gateway_order"
  }
}

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

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and the description corroborates with 'opens nothing by itself', which is helpful but repeats the safety profile. The genuinely additive content is the note that no public EZ Lawn Biller API exists, explaining why browser automation is required. It does not describe the shape or length of the returned instructions beyond listing screens/buttons/fields.

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 instruction — this returns steps and performs nothing — is front-loaded, but the third sentence is a long, dated research aside with 404 URLs that could be compressed to a single clause. The run-on second sentence packs three ideas before the reader learns the actual action.

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?

With no parameters and no output schema, the description does the necessary work by saying the return value is step-by-step procedural guidance and by pointing to the companion browser tools. It leaves minor gaps, such as whether the steps are account-specific or the error behavior if the page differs.

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 schema carries no semantics to compensate for and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 makes clear this tool does not create an order but returns step-by-step instructions (screens, buttons, fields) for placing a Gateway Order, and names the cotlet_browser_* tools as the actual executor. The verb is somewhat buried in a noun-phrase framing, and the sibling ez_lawn_biller_optimize_order is never differentiated, but an agent can tell what it gets back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit workflow context: call this first, then perform the action with cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. It states no exclusions or when-not-to-use conditions, and the relationship to sibling tools like optimize_order is left unaddressed.

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?