Skip to main content
Glama

Estimate details in EZ Lawn Biller

ez_lawn_biller_estimate_details
Read-onlyIdempotent

Estimate details 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_estimate_details"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already state readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the description earns credit for adding context: it says the tool only returns guidance and performs no action. The note that no public API exists and browser automation is required explains why the handoff exists. It does not describe the shape or limits of the returned guidance, such as its length or whether it is version-specific.

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 instruction and the cotlet_browser_* handoff are front-loaded and easy to act on. However, the API-discovery paragraph (404s on /api, /developers, /docs dated 11 Nov 2026, plus the QuickBooks note) is heavy justification text that does little to help the agent invoke the tool.

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, read-only guidance tool with no output schema, the description says what the output contains (screens, buttons, fields) and what to do next. The remaining gaps, such as output format and length, are minor for a tool this simple.

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 schema has zero parameters at 100% coverage, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description adds no confusion.

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 output: 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)'. This usefully corrects the misleading name, which reads like a data-fetch tool rather than an instruction generator. It does not explicitly separate itself from similar tools such as ez_lawn_biller_estimate_help or ez_lawn_biller_details, so the agent must infer that difference.

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 sets a clear workflow: use this tool to get instructions, then carry them out with the cotlet_browser_* tools in the user's Cloud Browser. It also states the negative constraint that the tool 'opens nothing by itself'. It gives no explicit rule for when to choose this over the sibling help tool or the plain details tool.

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