Skip to main content
Glama

Waive this late fee in EZ Lawn Biller

ez_lawn_biller_waive_this_late_fee
Read-onlyIdempotent

Waive this late fee 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_waive_this_late_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description is consistent with them by explicitly saying it 'opens nothing by itself.' Beyond annotations it adds genuinely useful behavior: the return value is procedural instructions keyed to screens, buttons and fields, and completion requires an external browser toolset. The API-availability note explains the constraint that motivates the workflow.

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 opening sentence is well front-loaded and the second sentence carries the key operational detail. The trailing API audit — specific dates, three URLs returning 404, and the QuickBooks FAQ reference — is disproportionate to a zero-parameter tool and adds provenance rather than actionable guidance, diluting an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 full annotation coverage and no output schema, the description covers what is returned and what to do next, which is largely sufficient. The remaining gap is target resolution: with no identifier parameter, the description should say how the agent establishes which late fee is meant before relying on the returned steps.

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 empty, so there is nothing to document and the baseline of 4 applies. The description does not need to explain parameter meaning, though it does leave implicit how 'this' late fee is resolved from conversation context.

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 action and resource ('waive this late fee') and then clarifies the actual mechanic: it 'returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That correction is important because the tool name reads like a direct mutation. The only shortfall is that it never contrasts itself with the sibling list tools like ez_lawn_biller_late_fees or ez_lawn_biller_customer_late_fees, so the agent must infer that those enumerate while this one resolves a single fee.

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 a clear follow-on instruction ('then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser'), which tells the agent this is a first step in a two-step flow. However, it never states when to prefer this over the sibling late-fee tools, what preconditions must hold (an existing overdue invoice, a specific fee already identified in conversation), or what to do if no late fee is in 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