Skip to main content
Glama

Customer impersonation in EZ Lawn Biller

ez_lawn_biller_customer_impersonation
Read-onlyIdempotent

Customer impersonation 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_customer_impersonation"
  }
}

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 declare readOnlyHint/idempotentHint/non-destructive/openWorldHint=false, and the description is consistent, adding the key behavioral fact that the tool performs no UI action itself and yields procedural text instead. It also explains why the browser route exists by documenting that no public API was found (404s on /api, /developers, /docs; QuickBooks via FAQ). It does not describe output shape or how much detail the steps contain.

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 functional core ('returns how to do it step by step; opens nothing by itself; then use cotlet_browser_* tools') is strong but is buried after a nominal opener that merely restates the title. The closing API-research sentence about 404s and the QuickBooks-only FAQ is verbose and reads like audit trail rather than selection guidance, though it does justify the browser-first workflow.

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, no-output-schema tool the description covers what matters: what comes back (step-by-step screens/buttons/fields), what it does not do (opens nothing), and how to act on the result. Only the exact format/scope of the returned instructions is left implicit, which is reasonable given no output schema is declared.

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 per the baseline this is a 4. There is nothing for the description to disambiguate, and the absence of inputs is consistent with a pure instruction-retrieval tool.

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 makes the real function clear: it returns step-by-step instructions for customer impersonation (screens, buttons, fields) and 'opens nothing by itself', so an agent knows this is a guidance tool rather than an action. Explicitly names the resource (customer impersonation) and the follow-up executor (cotlet_browser_* tools). It does not differentiate from the closely-named siblings ez_lawn_biller_preview_as_customer or ez_lawn_biller_staff_impersonation, which is the main gap.

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?

Usage context is stated clearly: call this first to get the procedure, then execute it with the cotlet_browser_* tools in the user's Cloud Browser. That is an actionable when-to-use statement. No exclusions or comparison against sibling tools with overlapping purpose (preview_as_customer, staff_impersonation) are given, so it stops short of a 5.

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