Skip to main content
Glama

Auto-Resume in EZ Lawn Biller

ez_lawn_biller_auto_resume
Read-onlyIdempotent

Auto-Resume 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_auto_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', which sets the agent's expectation that no browser side effects occur here. It also adds context the annotations cannot carry: the exact shape of the return value (step-by-step screens/buttons/fields) and the absence of a public EZ Lawn Biller API, which explains why a browser-based path is required.

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 purpose is front-loaded, but the trailing API paragraph is long and oddly specific (404s at /api, /developers, /docs on 11 Nov 2026) for a tool that takes no inputs. The mid-sentence 'and opens nothing by itself; then do it with...' is also awkwardly spliced, costing some scannability.

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 rich annotations and no output schema, the definition covers what it returns, that it has no side effects, and which tool family to use next. What is missing is what 'auto-resume' actually restores and any prerequisite account state, which an agent would need to judge applicability.

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 correctly implies no input is needed - the target is 'the user's own EZ Lawn Biller account', resolved from context rather than from arguments. With no parameters to document, the baseline of 4 applies.

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 clearly states the tool's actual output: a step-by-step guide (screens, buttons, fields) for performing auto-resume in the user's own EZ Lawn Biller account, and explicitly says it opens nothing itself. That distinguishes it as a guidance tool rather than an action tool, though 'Auto-Resume' itself is never defined (resume what - billing runs, paused schedules?), and it does not distinguish itself from the sibling ez_lawn_biller_resume.

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 concrete follow-up path - 'then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser' - which implies this tool is the first step in a chain rather than the executor. However, it never states the triggering condition (when an agent should call this versus ez_lawn_biller_resume or any other sibling), so the usage rule is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources