Skip to main content
Glama

Email portal password in EZ Lawn Biller

ez_lawn_biller_email_portal_password
Read-onlyIdempotent

Email portal password 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_email_portal_password"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety bar is lower. The description still adds real value beyond them by stating explicitly that it "opens nothing by itself" and that execution happens in a separate Cloud Browser session, plus the API-availability finding that explains the architecture. It does not describe output shape or how account selection is handled.

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 is front-loaded in the first sentence, and the second sentence carries the execution path. The closing sentence about 404s on /api, /developers and /docs is well-past the point where it affects invocation and reads as provenance justification rather than actionable guidance, but it is contained to one sentence.

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 guidance tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields) and what to do next. Nothing an agent needs in order to call it correctly is missing; only the boundary against the reset-password sibling is left implicit.

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 and the schema itself is complete. Baseline for a no-parameter tool applies; nothing in the description misleads about inputs.

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?

Uses a specific verb+resource ("Email portal password in the user's own EZ Lawn Biller account") and makes clear this returns instructions rather than performing the action, which is the key distinction from the cotlet_browser_* execution tools. It does not explicitly differentiate against the close siblings ez_lawn_biller_reset_portal_password or ez_lawn_biller_portal_settings, so an agent must infer which of the three it wants.

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?

Gives clear usage context: call this to get step-by-step screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Cloud Browser. It also explains why the browser route is required (no documented official API). It stops short of stating exclusions, e.g. that this does not reset a forgotten password, which is presumably what the sibling reset tool handles.

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