Skip to main content
Glama

New Staff in EZ Lawn Biller

ez_lawn_biller_new_staff
Read-onlyIdempotent

New 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_new_staff"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior beyond that: the tool performs no action, returns a procedural walkthrough with screens/buttons/fields, and requires a separate browser-tool step to actually make the change. It does not state prerequisites such as account login or staff-management permissions, which keeps it from a 5.

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 facts are front-loaded: what it returns, that it acts on nothing, and which tools to use next. The closing sentence about the API audit (404s on /api, /developers, /docs; QuickBooks as the only integration) is longer than needed but does justify why a browser-based path is the only option.

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?

With no parameters and no output schema, the description carries the burden of explaining the return value, and it does: a step-by-step procedure rather than data. It also names the follow-on tool family. Missing only prerequisites and any hint about what happens if the user lacks staff-management rights.

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 clarify beyond the schema. Baseline 4 applies; the description correctly makes no parameter claims and needs none.

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 resource (New Staff in the user's own EZ Lawn Biller account) and, crucially, clarifies the actual operation: it returns step-by-step instructions (screens, buttons, fields) and 'opens nothing by itself.' That distinguishes it from action-performing siblings like ez_lawn_biller_manage_staff or ez_lawn_biller_add_technician. It loses a point because 'New Staff' reads like a create action and no sibling is named to disambiguate the guidance-vs-action split.

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?

It gives clear sequencing: call this to get the procedure, then execute it with the cotlet_browser_* tools in the Cloud Browser. That is real when-to-use guidance plus the follow-up path. It stops short of explicit exclusions (e.g., 'if you want to change an existing staff member, use manage_staff'), so the agent must infer the boundary from the sibling name alone.

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