Skip to main content
Glama

Roles & Permissions in EZ Lawn Biller

ez_lawn_biller_roles_permissions
Read-onlyIdempotent

Roles & Permissions 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_roles_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered; the description adds genuinely new context by stating it performs no actions itself, that the output is procedural UI guidance, and that no public API exists (404s on /api, /developers, /docs) with QuickBooks as the only named integration. That API note materially changes agent planning. Minor gap: it does not describe the response shape or length of the returned procedure.

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 core intent is front-loaded, but the prose is convoluted: 'Returns how to do it in EZ Lawn Biller step by step' and the dated API-audit sentence ('No publicly documented ... API was found on 11 Nov 2026') read as research notes wedged into a tool description. The API fact is useful, but its phrasing and the client-name list ('from ChatGPT, Claude or any AI agent') add bulk without adding decision value.

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, read-only, output-schema-less guidance tool, the description covers what an agent needs: what it returns, that it has no side effects, and which tools to use afterward. The one loose end is that `cotlet_browser_*` is not represented in the provided sibling set, so the handoff target is named but not further characterized.

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?

There are zero input parameters (schema coverage 100% by definition, empty object), so there are no parameter semantics to document and the baseline of 4 applies. The description correctly implies no inputs are needed.

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 (Roles & Permissions in the user's EZ Lawn Biller account) and a specific output form (step-by-step instructions covering screens, buttons and fields), which distinguishes it from the many action-oriented `ez_lawn_biller_*` siblings. It falls short of a 5 because the pronoun 'it' in 'Returns how to do it' leaves the operation slightly less crisp than a direct verb+object statement.

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 clearly says this tool only retrieves guidance ('opens nothing by itself') and names the follow-up path: execute the steps using the cotlet_browser_* tools in the user's Cloud Browser. That is a usable when-to-use/which-tool split. There is no explicit exclusion clause (e.g., what to do if the step-by-step content is unnecessary), which keeps it at 4 rather than 5.

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