Skip to main content
Glama

Delete estimate job in EZ Lawn Biller

ez_lawn_biller_delete_estimate_job
Read-onlyIdempotent

Delete 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_delete_estimate_job"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces this by stating it 'opens nothing by itself'. It also adds why browser automation is required by documenting that no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; QuickBooks is the only named integration). It does not describe the return format or length of the step-by-step output.

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 behavior is front-loaded, but the second sentence is a long run-on mixing guidance, delegation to browser tools, and API audit findings. The dated 404 investigation (specific URLs, a future date) is supporting rationale rather than invocation-critical information and could be trimmed.

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, non-destructive guidance tool with no output schema, the description covers what it returns, what it does not do, and how to complete the task afterward. Only the shape of the returned instructions and any prerequisites (authentication, account state) remain unstated.

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?

There are zero parameters, so there is nothing to document and the schema is fully covered. The description correctly adds no parameter claims, keeping the contract unambiguous.

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 states a specific resource and action (deleting an estimate job), but crucially clarifies that the tool itself only returns step-by-step instructions (screens, buttons, fields) and performs no action. That distinction separates it from the actual browser-driving flow, though the name 'delete_estimate_job' still reads like a mutation tool, which the description has to undo.

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 gives a clear two-step usage pattern: call this first to learn the procedure, then execute it with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. It does not explicitly contrast with the many sibling delete_*/edit_* guidance tools, so an agent must infer that each sibling covers a different object.

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