Skip to main content
Glama

Skip held periods in EZ Lawn Biller

ez_lawn_biller_skip_held_periods
Read-onlyIdempotent

Skip 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_skip_held_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds the crucial behavioral fact that it "opens nothing by itself" and only returns procedural guidance, which must then be carried out via cotlet_browser_* tools. It also explains why browser automation is needed by noting the absence of a public API. It does not cover authentication or session prerequisites, keeping it below a 5.

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 purpose and the key caveat (returns instructions, opens nothing) are front-loaded, which is good. However, the phrase "from ChatGPT, Claude or any AI agent" is filler, and the API research paragraph listing 404 URLs and a date is longer than needed to convey "no official API, use the browser tools." It is not bloated overall, but several words do not earn their place.

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 guidance tool with no output schema, the description adequately explains the return value (step-by-step screens, buttons, fields) and the required next step via cotlet_browser_* tools. Combined with annotations covering the read-only safety profile, an agent has enough to call it correctly. It could still be clearer about what account or browser context must already be active.

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 meaning to add beyond the empty schema. The baseline for a parameterless tool is 4, and nothing in the description misrepresents the input surface.

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 verb and resource ("Skip held periods in the user's own EZ Lawn Biller account") and immediately clarifies that the tool returns step-by-step instructions rather than performing the skip itself. That correction is essential because the name implies an action. It does not explicitly distinguish itself from nearby siblings such as ez_lawn_biller_bill_held_periods, so it stops short of 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 Guidelines3/5

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

The description gives a clear workflow: call this tool, get screens/buttons/fields, then execute with the cotlet_browser_* tools in the Cloud Browser. That implies when to use it, but there is no explicit when-not guidance or routing among the many held-billing siblings (bill_held_periods, review_held_billing, held_billing_reminders). Usage is inferable rather than stated.

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