Skip to main content
Glama

Staff impersonation in EZ Lawn Biller

ez_lawn_biller_staff_impersonation
Read-onlyIdempotent

Staff 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_staff_impersonation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', so there is no contradiction. It adds genuinely useful context beyond the annotations: the shape of what comes back (step-by-step screens/buttons/fields) and the API-availability research explaining why browser tools are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operative information (what it returns, that it performs nothing, and the browser-tool follow-up) is front-loaded in the first two sentences. The closing API-research note is somewhat verbose but earns its place by justifying why an alternative execution path is required.

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 no-parameter, no-output-schema, read-only guidance tool, the description covers what it returns and what to do next. Minor gaps remain: no mention of the permission level needed to impersonate staff, and no forward reference to the customer impersonation variant for contrast.

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?

With zero parameters the baseline is 4; there is nothing for the description to disambiguate and the empty schema already caps expectations. The description correctly implies no inputs are needed, so no semantic gap remains.

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 states a specific verb and resource: it returns step-by-step staff-impersonation instructions ('screens, buttons, fields') for EZ Lawn Biller and explicitly says it 'opens nothing by itself', which corrects what the name alone would imply. It does not, however, distinguish itself from the sibling ez_lawn_biller_customer_impersonation, so an agent must infer which impersonation guide applies.

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?

Usage is implied by the name and by the hand-off sentence: run this first, then execute the steps with cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. There is no explicit when-not-to-use guidance and no routing between this and the customer-impersonation sibling, so the agent must infer the boundary.

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