EZ Lawn Biller by Cotlet

Move stop in EZ Lawn Biller

ez_lawn_biller_move_stop

Read-onlyIdempotent

Move stop 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_move_stop"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true; the description reinforces this with 'opens nothing by itself' and specifies the return content (screens, buttons, fields). The API-research note (404s on /api, /developers, /docs; QuickBooks named as the sole integration) explains why no direct-API route exists and browser automation is required, which is useful context an agent cannot get from 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 is front-loaded and short, but the first sentence wastes space on multi-platform boilerplate and the closing API-research paragraph carries incidental detail (exact 404 paths, dates, FAQ/manual citations) that is justification rather than selection guidance. Trimming those two bookends would leave a sharper definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 purpose, the nature of the return value, and the exact follow-up tooling. Nothing further is needed for an agent to select and sequence it correctly.

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 schema semantics to extend; the baseline of 4 applies. The description adds nothing beyond confirming the tool acts on the user's own account, which is consistent with 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 verb+resource pair 'Move stop' is stated, and the second sentence reveals the real function — returning step-by-step instructions rather than performing the move. However, 'stop' is never explained (a route stop? a service stop?) and the headline sentence is padded with boilerplate ('from ChatGPT, Claude or any AI agent'), so an agent must read past the title to learn that this is a guidance tool, not an action tool.

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 clearly delimits what this tool does not do ('opens nothing by itself') and names the follow-up path: perform the actual move with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. That is genuine when-to-use-then-what routing. It does not distinguish this from other EZ Lawn Biller stop tools such as lock_stop or cancel, so 4 rather than 5.

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?