EZ Lawn Biller by Cotlet

Mobile App Data in EZ Lawn Biller

ez_lawn_biller_mobile_app_data

Read-onlyIdempotent

Mobile App Data 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_mobile_app_data"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

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 and destructiveHint=false, and the description reinforces this with 'opens nothing by itself,' so there is no contradiction. It also discloses the return shape (step-by-step screens/buttons/fields) and the handoff to the browser tools, though the official-API digression adds little behavioral value.

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 operative content is front-loaded in the first two sentences, but the trailing API note about 404s on ezlawnbiller.com/api, /developers and /docs on 11 Nov 2026 is tangential detail that does not help an agent invoke the tool. The lead phrase 'Mobile App Data in the user's own ... account' is also awkwardly worded.

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-param, no-output-schema guide tool, the description covers delivery format and the follow-up path with browser tools. It still never says what 'mobile app data' actually encompasses, so an agent cannot judge whether this guide covers the topic at hand.

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?

Zero parameters with an empty object schema, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly implies no inputs are needed because it only returns instructions.

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 title promise 'Mobile App Data,' which reads as a data-retrieval tool, but the body reveals it actually returns step-by-step navigation instructions ('screens, buttons, fields'). The clarifying clause is buried after a confusing lead, and nothing distinguishes it from the sibling cotlet_app_guide.

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?

Useful sequencing is given: the tool 'opens nothing by itself' and the agent should 'then do it with the cotlet_browser_* tools in the user's ... Cloud Browser.' However, there is no guidance on when to pick this guide over cotlet_app_guide or the many ez_lawn_biller_* action tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EZ Lawn Biller by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?