Skip to main content
Glama

Chemical Cost in EZ Lawn Biller

ez_lawn_biller_chemical_cost
Read-onlyIdempotent

Chemical Cost 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_chemical_cost"
  }
}

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?

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, but the description adds the non-obvious behavioral fact that the tool 'opens nothing by itself' and only returns procedural instructions, which is exactly what prevents an agent from assuming it fetches live cost data. The API note explains why UI automation via the browser tools is required. Return format details (how long the steps are, whether they are structured) are not described.

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 behavioral disclosure is front-loaded and clear, but the opening phrase 'from ChatGPT, Claude or any AI agent' and the detailed 404 audit ('/api, /developers and /docs returned 404') add bulk beyond what an agent needs to act. The API audit could be compressed to a single clause justifying browser automation.

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 parameters, no output schema and a readOnly annotation, the definition covers what the tool returns, that it performs no action, and which tool family to use next. The missing piece is sibling differentiation against chemical_usage and material_cost_per_service, which matters given how many near-identical EZ Lawn Biller tools exist.

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 the baseline is 4 and there are no parameter semantics to compensate for. The description correctly implies no inputs are needed by framing the output as generic procedural guidance.

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 makes clear this returns a step-by-step 'how to' for finding Chemical Cost inside EZ Lawn Biller, listing the kind of content returned (screens, buttons, fields). It does not, however, distinguish this from close siblings like ez_lawn_biller_chemical_usage or ez_lawn_biller_material_cost_per_service, so an agent cannot tell from the text alone which of the three it should call.

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 follow-up path explicitly: after getting the steps, perform the action with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. That is genuine when-to-use and how-to-continue guidance. It gives no exclusion criteria or guidance on when a sibling tool would be the better choice instead.

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