EZ Lawn Biller by Cotlet

Changes after sending in EZ Lawn Biller

ez_lawn_biller_changes_after_sending

Read-onlyIdempotent

Changes after sending 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_changes_after_sending"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already establish read-only, non-destructive, idempotent behavior. The description adds meaningful context beyond them by stating that it returns screens/buttons/fields, opens nothing by itself, and requires browser tools for the actual change, though it does not address freshness or error behavior.

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 key behavior is front-loaded in the second sentence ('Returns how to do it... step by step'), and the official API note is relevant context. The first sentence is somewhat run-on and the API detail is longer than necessary, but the description remains focused.

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 the return format, lack of side effects, and the follow-on browser execution path. It still leaves ambiguous what 'changes after sending' concretely means and how it relates to sibling tools, so it is not fully complete.

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, and the description has no parameter semantics to explain. A baseline score of 4 is appropriate for a zero-parameter tool.

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 the EZ Lawn Biller task 'Changes after sending' and explains that the tool returns step-by-step instructions rather than performing the change. It does not specify exactly what 'changes after sending' refers to or distinguish this from sibling EZ Lawn Biller tools, so it falls short of a 5.

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 a clear usage path: get the step-by-step instructions here, then execute them with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. The API note further explains why no official API call is appropriate, but explicit exclusions or guidance on when to choose a sibling tool are absent.

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?