Skip to main content
Glama

Material Cost Per Service in EZ Lawn Biller

ez_lawn_biller_material_cost_per_service
Read-onlyIdempotent

Material Cost Per Service 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_material_cost_per_service"
  }
}

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds the non-obvious fact that invoking it performs no UI action and yields text-only instructions. The API note (no documented API at /api, /developers, /docs; QuickBooks named as the only integration) explains why navigation guidance is the only route, though the "11 Nov 2026" date is confusing and may read as stale or erroneous to an agent.

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 mechanism and the hand-off to cotlet_browser_* tools are correctly front-loaded. The closing API-research sentence is disproportionate for a tool definition, cites a specific future-dated audit with URL-level detail, and dilutes the actionable first two sentences.

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

Completeness3/5

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

With no parameters and no output schema, the description must carry the whole contract, and it does say the return is screen/button/field steps. It still leaves the agent unsure what "Material Cost Per Service" is in EZ Lawn Biller and what the returned steps will look like in shape or length, which matters when the next action is to drive a browser.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The only semantic gap is that it never says what subject the step-by-step guide is keyed to, but with no inputs there is no parameter meaning to add.

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 description states the mechanism ("Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)") and scopes it to the user's own EZ Lawn Biller account, which clarifies this is a guidance tool rather than a query. However, the subject itself, "Material Cost Per Service," is never explained (is it a report screen, a per-service calculation, a settings page?), and nothing distinguishes it from nearby siblings such as ez_lawn_biller_per_service_rates or ez_lawn_biller_chemical_cost.

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?

The description gives a clear consumption pattern: this tool returns instructions and "opens nothing by itself," after which the agent should act "with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." That is real when/how guidance that an agent can act on. It does not, however, give any when-not condition or route between the many other ez_lawn_biller_* navigation tools.

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