Skip to main content
Glama

Bill held periods in EZ Lawn Biller

ez_lawn_biller_bill_held_periods
Read-onlyIdempotent

Bill held periods 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_held_periods"
  }
}

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 and idempotentHint=true, so the safety profile is covered; the description adds real value by specifying the return shape (screens, buttons, fields) and explicitly stating it 'opens nothing by itself'. That resolves the potential confusion between the mutating verb 'Bill' and the read-only annotation, and the API-availability note explains why browser automation is required.

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?

The operative content — what it returns and what to do next — is front-loaded in the first two sentences. The trailing API-availability sentence is long and includes a hard-coded date, making it the least economical part of the description, though it still carries rationale.

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?

With no parameters, no output schema and full annotation coverage, the remaining burden is explaining return content and next steps, both of which are addressed. The description tells the agent what it gets back and which tool family to invoke afterwards, which is sufficient for a zero-parameter guidance tool.

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 no parameter semantics to document; baseline is 4. The description correctly implies a parameterless, single-purpose call rather than suggesting any filtering or targeting options that do not exist.

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 held periods in the user's own EZ Lawn Biller account') and clarifies the actual mechanism — it returns step-by-step instructions rather than performing the action itself. An agent could still confuse it with siblings like ez_lawn_biller_skip_held_periods or ez_lawn_biller_bill_now, which are never named.

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?

Gives a clear follow-on workflow ('then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser'), which implies when this tool is the right starting point. However, there is no explicit statement of when NOT to use it and no comparison to the closely related held-periods siblings, leaving selection between them to inference.

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