Skip to main content
Glama

Review held billing in EZ Lawn Biller

ez_lawn_biller_review_held_billing
Read-onlyIdempotent

Review held billing 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_review_held_billing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely useful behavior: nothing is opened, the return value is a step-by-step screen/button/field walkthrough, and no official API exists so browser automation is required. The API-discovery detail is a helpful justification for the browser-tool handoff.

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 message is front-loaded and clear, but the closing sentence about 404s on /api, /developers and /docs plus the FAQ/manual details is longer than the agent needs for tool selection. That rationale could be compressed to 'no public API exists; use the browser tools.'

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 instruction-retrieval tool with no output schema, the description covers what it returns, what it does not do, and which tool family continues the workflow. It stops short of describing the shape or granularity of the returned steps beyond screens/buttons/fields, but nothing critical is missing.

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 no parameters, so the schema carries no semantic burden and the baseline is 4. The description correctly describes a parameterless invocation and sets expectations for the instruction payload returned.

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 ('Review held billing in the user's own EZ Lawn Biller account') and immediately clarifies a non-obvious fact: the tool returns step-by-step instructions rather than performing the action. It does not distinguish itself from adjacent siblings like ez_lawn_biller_bill_held_periods or ez_lawn_biller_skip_held_periods, which is the main gap.

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 explicit when-to-use context ('from ChatGPT, Claude or any AI agent') and a concrete next step: perform the operation with the cotlet_browser_* tools in the Cloud Browser. It lacks any when-not-to-use condition or explicit routing against the held-billing siblings that might be confused with it.

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