Skip to main content
Glama

New recurring item in EZ Lawn Biller

ez_lawn_biller_new_recurring_item
Read-onlyIdempotent

New recurring item 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_recurring_item"
  }
}

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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them by explicitly saying it 'opens nothing by itself'. It adds real context beyond the annotations by explaining that no public API exists, which is why browser automation is required. The dated 404 investigation detail is more trivia than behavioral disclosure.

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 critical distinction (returns guidance, performs nothing) is front-loaded, which is good. But the trailing sentence about ezlawnbiller.com/api returning 404 on 11 Nov 2026 and the FAQ naming QuickBooks is long and does not help an agent decide or call the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input schema properties and no output schema, the description carries the full burden and does so: it states the return shape (step-by-step screens, buttons, fields) and the required follow-up tool family. An agent knows exactly what it will get and what to do next.

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 the baseline is 4. The description correctly implies nothing is configured at this stage and that all input will be supplied later through the browser tools, though it does not explicitly say that.

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 names a specific resource action (create a new recurring item) and, unusually, states that the tool only returns step-by-step instructions rather than performing the action. It does not distinguish itself from near-identically named siblings such as ez_lawn_biller_edit_recurring_item or ez_lawn_biller_recurring_service, so an agent must infer the difference.

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 does say what to do next — use the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser after reading the guide — which is genuine routing guidance. However, there is no explicit statement of when to prefer this over the many sibling create/edit recurring-item tools, so the usage boundary is only implied.

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