Skip to main content
Glama

Billing History in EZ Lawn Biller

ez_lawn_biller_billing_history
Read-onlyIdempotent

Billing History 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_billing_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety burden is light. The description nonetheless adds real behavioral facts beyond them: the tool opens nothing by itself, its return value is procedural text rather than account data, and no official EZ Lawn Biller API exists so a browser session is required. It does not say whether a browser session must already be open or what happens if none is.

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?

Front-loaded and reasonably tight: purpose, output form, and the follow-up tool are stated in the first two sentences. The trailing API-research sentence (404s at /api, /developers, /docs on 11 Nov 2026) is somewhat verbose but earns its place by justifying why browser automation is required.

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 tool with no output schema and full annotation coverage, the description supplies the essentials: what it returns, that it has no side effects, and what tool to use next. The one remaining gap is the practical prerequisite of an existing Cloud Browser session.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter meaning 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 states a specific resource (EZ Lawn Biller billing history) and clarifies the actual output: a step-by-step how-to (screens, buttons, fields) rather than the data itself, plus 'opens nothing by itself'. That corrects a misleading first impression from the tool name. It does not differentiate from the near-identical sibling ez_lawn_biller_billing_history_2, which keeps it from 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 Guidelines4/5

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

It gives a clear workflow context: use this to learn the steps, then perform them with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. What is missing is explicit when-not guidance and any differentiation from the duplicate billing_history_2 sibling, so it stops short of 5.

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