Skip to main content
Glama

Past-due recipients in EZ Lawn Biller

ez_lawn_biller_past_due_recipients
Read-onlyIdempotent

Past-due recipients 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_past_due_recipients"
  }
}

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, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still earns credit by explicitly stating it "opens nothing by itself" (confirming no side effects) and by documenting that no public EZ Lawn Biller API exists, which explains why browser automation is the only execution path. It does not describe the shape of the returned step list, keeping it below a 5.

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 point (returns steps, opens nothing, execute via browser tools) is front-loaded and clear. The trailing API-research paragraph, complete with URLs and a specific date, is disproportionate for a zero-parameter tool and reads more like provenance notes than guidance an agent needs to invoke it. The phrasing 'Returns how to do it' is also slightly awkward.

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-param, read-only guide tool with no output schema, the description covers what it yields, that it performs no actions, and which tool family to use to actually perform the task. The remaining gap is what the returned steps look like and whether a connected browser session is a precondition, but nothing essential for correct invocation is absent.

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 schema is an empty closed object, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no parameter talk, and the 'user's own account' framing usefully establishes whose data the steps apply to.

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 makes clear this is a guidance/how-to tool for finding past-due recipients, not a data-fetching tool: it "returns how to do it ... step by step (screens, buttons, fields)." That is a specific enough verb+resource combination for an agent to select it. It does not, however, differentiate itself from the many other similarly-shaped ez_lawn_biller_* how-to siblings, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is usable sequencing guidance: this tool "opens nothing by itself," and the actual work is done afterward "with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." That tells the agent this is a first step, not an executor. Missing is any when-not guidance or explicit routing among the many sibling ez_lawn_biller_* tools, so usage is only implied by context.

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