Skip to main content
Glama

New On-Demand Customer in EZ Lawn Biller

ez_lawn_biller_new_on_demand_customer
Read-onlyIdempotent

New On-Demand Customer 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_new_on_demand_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive. The description adds genuinely non-redundant behavior: it returns a step-by-step procedural guide for the user's own account, performs no action itself, and hands execution off to the cotlet_browser_* tools. That is exactly the kind of clarification a read-only annotation cannot convey on its own.

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 is front-loaded and useful, but the trailing sentence about the official API not being found on '11 Nov 2026' (a future date) is tangential justification rather than operational guidance, and the opening phrase duplicates the tool title instead of stating the action.

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 output schema, the description correctly explains what comes back (step-by-step screens, buttons, fields) and what to do next (cotlet_browser_* tools in the Cloud Browser). For a zero-parameter, non-destructive helper, that covers nearly everything an agent needs, short of sibling differentiation.

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 nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% and the empty object is self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does eventually state the real behavior: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' However, the leading sentence ('New On-Demand Customer in the user's own EZ Lawn Biller account') reads like a creation action and only gets corrected two clauses later, and it never distinguishes this from siblings such as ez_lawn_biller_new_customer, ez_lawn_biller_create_customer, or ez_lawn_biller_new_one_time_service.

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?

There is a usable workflow implied: get the guide here, then perform the steps with cotlet_browser_* tools inside the EZ Lawn Biller Cloud Browser. What is missing is any condition for choosing this tool over the many adjacent customer-creation siblings, so the agent has context but no selection criteria.

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