Skip to main content
Glama

Manage EZ Lawn Biller Plan in EZ Lawn Biller

ez_lawn_biller_manage_ez_lawn_biller_plan
Read-onlyIdempotent

Manage EZ Lawn Biller Plan 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_ez_lawn_biller_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description reinforces this by stating it "opens nothing by itself" — no navigation or mutation occurs until browser tools are used. It also proactively explains why browser automation is required (no public API, 404s on /api, /developers, /docs). Beyond the annotations, it does not describe the shape or length of the returned instructions, but the safety profile is clearly and consistently conveyed.

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?

Three sentences, reasonably front-loaded on the key insight that this only returns instructions. But "EZ Lawn Biller" is repeated six times, and the API-availability research note (dates, 404 paths, QuickBooks mention) is disproportionately detailed for a zero-parameter guidance tool, diluting the actionable message.

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 parameterless, non-destructive instruction-returning tool with annotations and no output schema, the description covers what it does, what it does not do, and the correct follow-up tool family. The main gap is that it never defines what "Plan" refers to or roughly what the returned steps cover, so the agent must infer relevance.

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 and the schema is fully closed (additionalProperties=false), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter semantics are needed or missing.

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 verb "Manage" is vague and the resource "Plan" is ambiguous (subscription plan? billing plan?), so the agent cannot immediately tell what object is touched. However, the second sentence does clarify the real function: the tool returns step-by-step UI instructions for EZ Lawn Biller and performs no action itself. That functional clarification is the most valuable part, but it arrives after a generic title-style opening.

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?

The description gives a usable workflow: call this first to get the screens/buttons/fields, then execute with the cotlet_browser_* tools. That is real when-to-use guidance. It does not distinguish this tool from the many sibling ez_lawn_biller_* tools or say when not to call it (e.g., when the agent already knows the steps), leaving the choice largely implicit.

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