Skip to main content
Glama

Billing history in EZ Lawn Biller

ez_lawn_biller_billing_history_2
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_2"
  }
}

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, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavior facts — that it performs no action itself and that no public API exists (so the browser tools are the only route) — but says nothing about the shape or size of the returned guidance, such as formatting or verbosity.

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 is front-loaded in the first clause, the non-action disclaimer follows immediately, and the next step is stated before the supporting API rationale. The closing API-audit sentence (404 URLs, date, QuickBooks mention) is somewhat verbose for the value it adds, but it does justify 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, read-only tool with full annotation coverage and no output schema, the description covers what an agent needs: what comes back (ordered steps with screens/buttons/fields), that nothing is mutated, and which tools to use next. The remaining gap is disambiguation from the identically purposed sibling, which would prevent a wrong-tool selection.

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 a closed empty object, so there is no parameter meaning for the description to add. The baseline of 4 applies; no gaps exist here.

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 names a specific resource (billing history in EZ Lawn Biller) and a specific output (step-by-step screens, buttons and fields), and it explicitly states it 'opens nothing by itself,' so an agent knows this is a documentation/guidance tool rather than an executor. It does not, however, differentiate itself from the near-identically named sibling ez_lawn_biller_billing_history, leaving ambiguity about which of the two to call.

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 clear workflow context: call this first to get steps, then perform them with the cotlet_browser_* tools in the user's Cloud Browser. What is missing is any when-not guidance or routing among alternatives — notably the duplicate billing_history sibling — leaving the agent to infer which variant applies.

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