Skip to main content
Glama

Low-stock alerts in EZ Lawn Biller

ez_lawn_biller_low_stock_alerts
Read-onlyIdempotent

Low-stock alerts 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_low_stock_alerts"
  }
}

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is given. The description reinforces this with 'opens nothing by itself' and adds genuinely new context about the absence of a public API and QuickBooks being the only named integration, explaining why browser automation is required. It stops short of describing the shape or granularity of the returned instructions.

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 two operational sentences are tight and useful, but the trailing API-research note with dated 404 results is a digression that consumes roughly a third of the text. The core action ('returns step-by-step instructions') should be front-loaded rather than following a topic phrase that implies configuration.

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 covers what is returned (screens, buttons, fields), that nothing is mutated, and which tools to use next. Only the return format/verbosity is unspecified, which is a minor gap.

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, and the description correctly implies a parameterless call scoped implicitly to 'the user's own EZ Lawn Biller account'. Baseline 4 applies since there are no parameters to explain.

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 names the concrete topic (low-stock alerts) and states the actual output: 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)'. The leading phrase reads like a feature-setting tool, so the real verb ('returns guidance') only lands in the second sentence, but the distinction from mutating siblings like ez_lawn_biller_add_stock is still clear.

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 gives an explicit workflow: call this to obtain steps, then execute them 'with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser', and it states this tool 'opens nothing by itself'. That is clear context for when to use it, though no when-not condition or named sibling alternative is offered.

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