Skip to main content
Glama

Manage Staff in EZ Lawn Biller

ez_lawn_biller_manage_staff
Read-onlyIdempotent

Manage Staff 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_manage_staff"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so safety is covered structurally. The description adds real value beyond that: it states the tool "opens nothing by itself" (no side effects), specifies the return shape (step-by-step screens, buttons, fields), and names where the action must actually happen. It does not cover authorization, account prerequisites, or rate limits, which keeps it out of 5 territory.

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?

Three sentences, front-loaded with the verb and the key behavioral fact (it only returns guidance). The closing sentence about the missing public API earns its place by explaining why the browser tools are the execution path, though the dated evidence detail ("returned 404", "11 Nov 2026") is slightly more provenance than an agent needs to act.

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-parameter, read-only guidance tool with no output schema, the description covers purpose, return content, and the handoff to browser tools, which is largely sufficient. The remaining gap is scope: "manage staff" spans add/remove/role operations, and the description never bounds what topics this guidance covers or how it relates to the granular staff siblings.

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 schema has zero parameters and 100% description coverage, so there is nothing for the description to disambiguate. The description correctly implies no inputs are required. Baseline 4 applies for a parameterless 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 clear this tool returns procedural guidance ("how to do it in EZ Lawn Biller step by step (screens, buttons, fields)") rather than performing the action itself. That is a specific and non-obvious purpose. It does not, however, distinguish itself from the staff-related siblings (ez_lawn_biller_new_staff, ez_lawn_biller_remove_staff, ez_lawn_biller_staff_role), which all plausibly cover parts of "manage staff."

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?

There is strong routing guidance for the follow-up step: "opens nothing by itself; then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." That tells the agent this is the planning/instruction step and names the execution alternative. But it gives no guidance on when to pick this tool over the concrete staff siblings, so the choice within the staff tool family is left to inference.

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