Skip to main content
Glama

Edit estimate job in EZ Lawn Biller

ez_lawn_biller_edit_estimate_job
Read-onlyIdempotent

Edit estimate job 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_edit_estimate_job"
  }
}

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?

The annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so safety is covered structurally; the description adds genuinely non-derived behavior by stating it "opens nothing by itself" and only returns procedural guidance. The closing note that no public API exists (documented 404s, QuickBooks as the only named integration) explains why a browser-based path is required and preempts an agent hunting for an API route. It stops short of stating prerequisites such as a signed-in Cloud Browser session or what the returned steps look like in shape/length.

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 most decision-relevant fact (it returns instructions rather than editing) is delayed behind filler about being usable from "ChatGPT, Claude or any AI agent." The API-404 paragraph is relevant but long and reads like provenance research rather than call guidance. Tightening the opening to lead with the return-and-handoff behavior would improve front-loading.

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 parameterless, side-effect-free guidance tool with no output schema, the description covers what comes back (step-by-step screens, buttons, fields) and what to do next (cotlet_browser_* tools). The gap is environmental: it does not state that the user must already have an EZ Lawn Biller Cloud Browser session, which the handoff instruction silently assumes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters the default baseline is high, and the schema (empty object, additionalProperties=false) leaves nothing to misread. However, the description never explains how a specific estimate job is targeted given no identifying parameter at all — presumably context comes from the user's browser session — and that unstated mechanism is exactly what an agent needs to avoid calling this expecting per-job output.

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 concrete verb and resource ("Edit estimate job") and, unusually, immediately reframes the real function: it "returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)." That clarification rescues an otherwise misleading name. It does not, however, distinguish this from the sibling ez_lawn_biller_edit_estimate or explain what an "estimate job" is versus an estimate, so an agent must guess which of the two to pick.

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 clear workflow instruction: call this first, then "do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." That tells the agent where this tool sits in the sequence. Missing is any when-not guidance or routing among the several overlapping edit_* siblings (edit_estimate, edit_estimate_job, estimate_help), which is the main selection ambiguity an agent faces here.

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