Skip to main content
Glama

Portal settings in EZ Lawn Biller

ez_lawn_biller_portal_settings
Read-onlyIdempotent

Portal settings 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_portal_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds meaningful behavior: it returns procedural guidance rather than data, and explicitly 'opens nothing by itself,' so the agent knows no side effects occur. The appended note that no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; QuickBooks the only named integration) further explains why browser automation is the only execution path.

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 purpose and the follow-up instruction are front-loaded in the first two clauses, which is the right ordering. The trailing API-availability paragraph is somewhat verbose for its value, but it does justify the browser-tool handoff rather than being pure filler.

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?

For a zero-parameter, read-only knowledge tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields), what is not performed (nothing opened), and the next step (cotlet_browser_* tools). There is no material gap an agent would need filled before invoking it.

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 disambiguate; the baseline for a parameterless schema applies.

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 (portal settings) and clarifies the tool's real output: 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That distinguishes it from action-oriented siblings, though related settings siblings like ez_lawn_biller_email_portal_password and ez_lawn_biller_reset_portal_password are never named or differentiated.

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 a clear workflow: call this to obtain instructions, then execute 'with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' That is actionable context, but there are no explicit when-not-to-use conditions or routing to the closely related portal-password siblings.

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