Skip to main content
Glama

Supplies used in EZ Lawn Biller

ez_lawn_biller_supplies_used
Read-onlyIdempotent

Supplies used 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_supplies_used"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it explicitly says it 'opens nothing by itself', which prevents the agent from assuming side effects, and it discloses that no public API exists so the only path is browser automation. That is real behavioral context the annotations do not carry. It stops short of describing the size or shape of the returned guidance.

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 point (returns guidance, do it via cotlet_browser_*) is buried after a vague topic phrase, and the closing paragraph about 404 URLs and QuickBooks is dated boilerplate. Two of the three sentences earn their place, but the ordering is not front-loaded.

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?

For a parameterless read-only guidance tool with no output schema, the description covers the essential contract: it returns procedural steps and performs no action. It leaves unstated what the returned steps look like in structure and whether they are tied to a specific screen or workflow area, which would help an agent decide whether to call it at all.

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 (100% schema coverage trivially), so the baseline of 4 applies. Nothing in the description is needed to explain inputs, and nothing misleading is offered.

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 eventually reveals that this tool returns step-by-step instructions ('screens, buttons, fields') rather than supply-usage data, which is important but arrives late and mildly conflicts with the name/title reading of 'supplies used'. The opening sentence 'Supplies used in the user's own EZ Lawn Biller account' does not state a verb or define the resource concretely, and nothing distinguishes it from the many topic-named siblings.

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?

It does give a follow-on path: after this, perform the action with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. However, it never says when to choose this tool over a sibling like the activity or billing-history tools, nor what input conditions are required.

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