Skip to main content
Glama

Download PDF in EZ Lawn Biller

ez_lawn_biller_download_pdf_2
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_2"
  }
}

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered; the description adds genuinely new behavioral facts beyond that — it never opens anything itself, it returns screen/button/field-level instructions, and the required execution path is the cotlet_browser_* tools. The API-availability research further explains why browser automation is the only route. It stops short of describing the returned instruction format.

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 ('opens nothing by itself') is tucked mid-sentence after the misleading 'Download PDF' opener, so the reader must re-parse the tool's nature. The closing paragraph about 404s on /api, /developers and /docs is background justification rather than actionable instruction, and 'EZ Lawn Biller' is repeated five times.

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?

With no parameters and no output schema, the description must carry the burden of explaining what comes back and which document is targeted. It does describe the return as step-by-step screens/buttons/fields and names the execution tool, but it never identifies which PDF, leaving ambiguity against the many sibling PDF tools.

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?

There are zero parameters and schema coverage is 100%, so there is nothing for the description to disambiguate at the parameter level. Baseline for a no-parameter tool 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 name and first sentence say 'Download PDF in the user's own EZ Lawn Biller account,' which reads like the tool performs the download, but the second clause clarifies it 'Returns how to do it ... step by step' and 'opens nothing by itself.' The actual behavior (a procedural-instructions tool, not an action tool) is stated, but only after a misleading opener, and the description never says which PDF among the many sibling PDF tools it covers.

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 usable workflow: call this, then execute the steps 'with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' However, it offers no differentiation from the near-identical siblings ez_lawn_biller_download_pdf, ez_lawn_biller_open_pdf, or ez_lawn_biller_download_schedule_pdf, so an agent cannot tell which variant applies to which document.

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