EZ Lawn Biller by Cotlet

Add Technician in EZ Lawn Biller

ez_lawn_biller_add_technician

Read-onlyIdempotent

Add Technician 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_add_technician"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations mark it readOnlyHint=true, yet the name implies a write, and the description resolves that tension head-on: it 'opens nothing by itself' and only returns screens, buttons and fields. It also discloses the integration landscape (no public API, only QuickBooks per the vendor's FAQ), which annotations cannot convey. Return mechanics are described at a high level only, so a 4.

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?

Front-loaded and purposeful, but the closing API-audit sentence (404 paths, FAQ, QuickBooks) is longer than it needs to be for its payoff and packs multiple clauses into single sentences. Trimming the audit detail to one clause would improve it.

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 no-parameter, no-output-schema helper, the definition covers what is returned (step-by-step instructions), that nothing is executed, and which tool family takes over next. The handoff details, such as whether state must be passed to the cotlet_browser_* call, are the only gap.

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?

With zero parameters the baseline is 4; there is nothing parameter-wise for the description to compensate for, and it adds no confusing pseudo-parameter claims. Note only that the user's EZ Lawn Biller account is implicitly determined by session context, not schema.

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 gives a specific verb and resource ('Add Technician in the user's own EZ Lawn Biller account') and immediately clarifies that the tool returns step-by-step instructions rather than performing the add. The distinction from the read-only technician_* siblings is left implicit, keeping it 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 Guidelines4/5

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

It states the workflow clearly: call this first to get the click-by-click steps, then use the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser to actually perform them. 'Opens nothing by itself' rules out the most likely misassumption. No explicit when-not-to-use or named alternative is given, so it is not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EZ Lawn Biller by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?