Skip to main content
Glama

Download PDF in EZ Lawn Biller

ez_lawn_biller_download_pdf
Read-onlyIdempotent

Download 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_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the facts annotations cannot express: that the call returns instructions with screens/buttons/fields and performs no side effect or file opening, and that execution must be delegated to cotlet_browser_* tools. This resolves a genuine name-versus-behavior ambiguity. It stops short of saying what the response payload looks like (prose guide vs. structured steps).

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 behavioral clarification is front-loaded in the first two sentences, which is good. But the trailing API-research paragraph (dated lookups of /api, /developers, /docs, and a QuickBooks note) does not help an agent select or invoke the tool and reads as leftover investigative context. It costs space without improving the call decision.

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 zero-parameter, no-output-schema instruction tool, the definition explains what it returns and what to do afterward, which is most of what is needed. What is missing is disambiguation across the large PDF sibling family, which is the main decision an agent faces here. The API-availability note is context about the product, not about using this tool.

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 is 4 and there is no schema semantics the description needs to duplicate. Nothing in the description misdescribes inputs, and it correctly implies a parameterless call.

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 (EZ Lawn Biller PDF) and clarifies a non-obvious behavior — it returns step-by-step instructions and 'opens nothing by itself' rather than producing a file. However, the name/title ('Download PDF') points at a file-producing action that the description then negates, and it offers no differentiation from the many near-identical siblings (download_pdf_2, download_schedule_pdf, open_pdf, statement_pdf, pay_statement_pdf). An agent cannot tell from this text which PDF tool covers which document.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is a handoff ('then do it with the cotlet_browser_* tools in the Cloud Browser'), which describes the next step rather than when to select this tool over its siblings. With five-plus sibling PDF tools in the catalog, the absence of any routing rule is a real gap. There are no exclusions or preconditions 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