EZ Lawn Biller by Cotlet

Offer PayPal automatic payments again in EZ Lawn Biller

ez_lawn_biller_offer_paypal_automatic_payments_again

Read-onlyIdempotent

Offer PayPal automatic payments again 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_offer_paypal_automatic_payments_again"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description is fully consistent with them, adding meaningful behavior the annotations cannot express: the tool returns a procedure (screens, buttons, fields) and performs no UI action, so a browser tool chain is required to actually apply it. The dated API-discovery note further explains why no direct API path exists.

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 behavior and the required follow-up browser step are front-loaded in the first two sentences and stated without waste. The trailing API-provenance note (specific 404 URLs and a date) is the longest and least actionable part, though it does justify the browser-tool dependency.

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, closed-world tool with no output schema, the description covers everything an agent needs: what it returns (a step-by-step procedure), that it mutates nothing, and which tool family carries out the actual change. Nothing material is left undetermined.

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 parameter semantics to convey beyond what the empty schema already states. Baseline of 4 applies; no additional guidance is needed or missing.

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 a specific action and resource (re-offering PayPal automatic payments in the user's own EZ Lawn Biller account) and clarifies the crucial nuance that it returns step-by-step instructions rather than performing the change. The 'again' framing distinguishes it implicitly from the plain automatic_payments sibling, but no sibling is named outright.

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 does give a follow-up workflow ('then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser') and states that it opens nothing by itself, which tells the agent what this tool is not for. However, there is no explicit when-to-use versus ez_lawn_biller_automatic_payments or ez_lawn_biller_cancel_automatic_payments, and no stated exclusions or prerequisites.

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?