EZ Lawn Biller by Cotlet

Inventory item in EZ Lawn Biller

ez_lawn_biller_inventory_item

Read-onlyIdempotent

Inventory item 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_inventory_item"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, and the description reinforces this with "opens nothing by itself," explicitly telling the agent it will not mutate the account. It also explains why a browser route is needed (no public API as of 11 Nov 2026, 404s on /api, /developers, /docs; QuickBooks the only named integration), which is genuinely useful context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it states what the tool is, then what it returns, then how to continue, then the API caveat. Every clause carries information, and the API-probe narrative is kept brief while still justifying the two-step workflow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what the tool returns (step-by-step screens, buttons and fields), what it does not do (opens nothing), how to complete the action (cotlet_browser_* tools) and why the browser path is needed (no public API). With no parameters and no output schema, that is enough for an agent to invoke it correctly.

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 the description correctly presents no argument-handling details. Nothing is missing on this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title and opening phrase ("Inventory item in the user's own EZ Lawn Biller account") largely restate the name; the real purpose only emerges in the second sentence, which says it returns step-by-step instructions (screens, buttons, fields). It never clarifies which inventory operation this covers, nor how it differs from siblings such as ez_lawn_biller_add_item, ez_lawn_biller_inventory_value or ez_lawn_biller_inventory_checklist.

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 one concrete workflow cue: run this first, then act with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. But there is no guidance on when to choose this over the many inventory/config siblings, and no exclusions stating what this tool does not cover.

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?