Skip to main content
Glama

Reactivate stopped line in EZ Lawn Biller

ez_lawn_biller_reactivate_stopped_line
Read-onlyIdempotent

Reactivate stopped line 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_reactivate_stopped_line"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotent and non-destructive, and the description usefully reinforces that by saying the tool opens nothing and only returns guidance. Beyond that it adds little operational context — no indication of output format detail, length, or failure behavior — and the closing note about the missing public API is tangential rather than behavioral.

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 first sentence front-loads the purpose and the second carries the key routing information. However, 'from ChatGPT, Claude or any AI agent' is filler, and the final sentence about 404s on ezlawnbiller.com/api, /developers and /docs is a long justification for a single fact (no official integration) that does not help an agent invoke the tool.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter guidance tool with no output schema, the description does say what comes back (step-by-step screens, buttons, fields) and how to act on it. It never explains what a 'stopped line' is in EZ Lawn Biller terms, and gives no clue about the resulting response's structure or size, leaving a gap an agent may hit on first call.

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 baseline is 4 and there is no parameter semantics to explain. The description correctly implies no input is needed by describing it as a pure guidance call.

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?

States a specific verb+resource (reactivate stopped line) and clarifies the surprising part — that the tool only returns step-by-step instructions rather than performing the action. It does not, however, distinguish itself from close siblings such as ez_lawn_biller_reactivate or ez_lawn_biller_reactivate_customer, so an agent must guess which of these to pick.

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?

Gives an explicit workflow: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Cloud Browser. It clearly states what this tool does not do ('opens nothing by itself'), though it offers no conditions for when to prefer the sibling reactivate tools.

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