Skip to main content
Glama

Notice dry run in EZ Lawn Biller

ez_lawn_biller_notice_dry_run
Read-onlyIdempotent

Notice dry run 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_notice_dry_run"
  }
}

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it 'opens nothing by itself' and only produces procedural guidance, and it explains the absence of a public EZ Lawn Biller API, which justifies the browser-based follow-up path.

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 key constraint ('returns how to do it step by step ... opens nothing by itself') is front-loaded and well placed. However, the opening phrase largely restates the tool name and title, and the audience enumeration ('from ChatGPT, Claude or any AI agent') adds no decision value; the API-availability paragraph is long but does earn some of its space by explaining why browser tools are needed.

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 advisory tool with full annotation coverage and no output schema, the description supplies the essential missing pieces: what is returned (screens, buttons, fields), that nothing is executed, and how to proceed afterwards. Only the relationship to sibling notice tools is left unstated.

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 of 4 applies and there is no parameter meaning for the description to add. Nothing in the description misleads about inputs.

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 a specific verb and resource ('Notice dry run') and immediately clarifies the surprising part: it returns step-by-step instructions (screens, buttons, fields) rather than performing the action. It does not explicitly contrast with nearby siblings such as ez_lawn_biller_notice_preview or ez_lawn_biller_statement_dry_run, so the agent must infer which dry-run variant applies.

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 clear sequencing guidance: call this first, then execute with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. What is missing is an explicit 'do not use this when...' clause distinguishing it from notice_preview or the statement dry run, so alternatives are implied rather than stated.

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