Skip to main content
Glama

Bill the customer in EZ Lawn Biller

ez_lawn_biller_bill_the_customer
Read-onlyIdempotent

Bill the customer 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_bill_the_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, and the description is consistent with them ('opens nothing by itself'). It adds value beyond the structured fields by explaining the return shape (screens, buttons, fields) and by documenting the absence of a public EZ Lawn Biller API, including the checked endpoints and date, which explains why browser automation is the only path.

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?

Purpose and the read-only guarantee are front-loaded in the first sentence, with the follow-up mechanism second. The API-research sentence is long but earns its place by justifying the browser-based workflow rather than a direct integration.

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 what it returns and what it does not do. Annotations carry the safety profile. The only shortfall is the unaddressed question of how the customer is scoped when no parameters exist.

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 nothing for the description to clarify about inputs and the baseline is a 4. One minor gap: with no parameters, it never explains how the target customer is identified (presumably conversational context), which an agent might wonder about.

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 and resource ('Bill the customer in ... EZ Lawn Biller') and immediately clarifies the crucial mechanism: it 'Returns how to do it ... step by step (screens, buttons, fields) and opens nothing by itself.' That distinguishes it from tools that actually act. It does not, however, differentiate itself from close billing siblings such as ez_lawn_biller_bill_now or ez_lawn_biller_bill_held_periods, so an agent must infer which billing variant 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 Guidelines3/5

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

The description gives a usable workflow: call this to get the steps, 'then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' That is clear guidance for the follow-up action. It stops short of saying when-not to use this versus the other billing siblings, leaving variant selection implicit.

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