Skip to main content
Glama

Staff role in EZ Lawn Biller

ez_lawn_biller_staff_role
Read-onlyIdempotent

Staff role 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_role"
  }
}

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: 'opens nothing by itself' tells the agent this is guidance-only and requires a separate execution step, and the API-availability note explains why browser automation is the path. It does not describe the shape of the returned steps (length, format), which would have completed the picture.

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 core instruction is front-loaded in the first two sentences, but the closing sentence about 404s on /api, /developers and /docs and the QuickBooks-only FAQ detail is verbose and largely incidental. It justifies the browser-tool workflow but could be compressed to one clause without losing meaning.

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, no output schema and full annotation coverage, the description needs only to explain the workflow, which it does. What is missing is scope: whether this covers creating a role, assigning one to staff, or editing permissions, which matters given four similarly named siblings. Adequate but not complete.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no inputs are needed by framing the call as a lookup keyed on the task itself.

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 says it returns step-by-step instructions (screens, buttons, fields) for the 'staff role' task in EZ Lawn Biller, which is a specific verb+resource. However, 'staff role' is left ambiguous against close siblings such as ez_lawn_biller_custom_role, ez_lawn_biller_manage_staff, ez_lawn_biller_new_staff and ez_lawn_biller_remove_staff — the reader cannot tell which staff-role operation this covers. It distinguishes itself clearly from the browser tools but not from its own family.

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 two-step workflow: call this to get the procedure, then execute it with the cotlet_browser_* tools in the user's Cloud Browser. It never states when to prefer this over the other ez_lawn_biller_* staff/role tools, nor any preconditions (e.g., being signed in). Usage is implied by the name rather than spelled out.

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