Skip to main content
Glama

Permission controls in EZ Lawn Biller

ez_lawn_biller_permission_controls
Read-onlyIdempotent

Permission controls 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_permission_controls"
  }
}

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 readOnly, idempotent, non-destructive, and non-open-world, so the safety bar is met structurally. The description adds meaningful behavior beyond them: it produces no side effects and opens no screens itself, and it discloses the absence of a documented public API (404s on /api, /developers, /docs; QuickBooks-only integration), justifying the browser handoff. It does not describe rate limits or result formatting, so it stops short of 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 core instruction and the handoff are front-loaded in the first sentence, with the API-availability caveat appended as justification. The 404/FAQ/manual detail is somewhat verbose for a single caveat but does earn its place by preventing the agent from attempting API integration. No redundant restatement of the title.

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 zero-parameter, output-schema-less informational tool, the description covers what is returned (step-by-step screens, buttons, fields) and what is not done (no action taken), and rich annotations cover the safety profile. What is missing is minor, such as what to do if the user's EZ Lawn Biller version differs from the documented steps.

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?

Zero parameters, so the baseline of 4 applies; the empty object schema matches a parameterless documentation lookup. The description also confirms the tool returns a static how-to rather than performing account lookups, which is the only semantic point a zero-param tool needs.

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 concrete deliverable: step-by-step instructions (screens, buttons, fields) for permission controls in EZ Lawn Biller. It explicitly contrasts itself with the action-performing path ('opens nothing by itself; then do it with the cotlet_browser_* tools'), so an agent can tell it apart from browser automation, though it does not differentiate itself from the many ez_lawn_biller_* sibling tools.

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?

Clear usage model: call this first to learn the procedure, then execute it with cotlet_browser_* in the user's Cloud Browser. It also explains why no direct API path exists, which steers the agent away from attempting API calls. It does not explicitly state when not to use it (e.g., for other EZ Lawn Biller topics), but the context is unambiguous.

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