Skip to main content
Glama

Download schedule PDF in EZ Lawn Biller

ez_lawn_biller_download_schedule_pdf
Read-onlyIdempotent

Download schedule PDF 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_download_schedule_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, but the description adds genuinely useful behavior beyond them: this call opens nothing by itself and only returns screens, buttons and fields, and no public EZ Lawn Biller API exists (site paths returned 404, QuickBooks is the only named integration). That explains why browser automation is required rather than an API call.

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 opening sentence is contradictory on first read ('Download schedule PDF... opens nothing by itself'), which could mislead before the clarification lands, and the closing API/404 research note is tangential context. The content is front-loaded and not padded, but the ordering obscures the core behavior.

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?

With no parameters, no output schema and a full annotation set, the description covers enough: what is returned (step-by-step screens, buttons, fields), that no side effect occurs, and which tool family to use next. Only the sibling routing is missing.

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 schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 does state the resource (the schedule PDF in EZ Lawn Biller) and reveals the odd behavior that it returns step-by-step instructions rather than a file, which reconciles the misleading verb 'download' in the name. However, it never distinguishes itself from close siblings such as ez_lawn_biller_download_pdf, ez_lawn_biller_download_pdf_2, or ez_lawn_biller_open_schedule_pdf, so an agent cannot tell which of these near-identical tools to pick.

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 gives a clear forward workflow: call this to get instructions, then perform the action with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. What is missing is any when-not guidance or comparison against the many other download/open PDF siblings, so tool selection among the family is left to inference.

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