Skip to main content
Glama

Income in EZ Lawn Biller

ez_lawn_biller_income
Read-onlyIdempotent

Income 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_income"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so safety is covered structurally. The description still adds real value by stating the tool opens nothing by itself and by documenting the absence of a public API (404s on /api, /developers, /docs, QuickBooks as the only integration), which explains why browser automation is required. It does not describe the shape or length of the returned instructions.

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 behavior is front-loaded and the follow-up routing is stated early, which is good. The API-discovery sentence is long and includes dated detail (11 Nov 2026, specific URL 404s) that adds bulk beyond what most callers need to decide or invoke, and the opening clause 'Income in the user's own EZ Lawn Biller account from ChatGPT, Claude or any AI agent' is awkward.

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?

With zero parameters and no output schema, the description carries the burden of explaining the return value, and it does so adequately: step-by-step screens, buttons and fields, plus which tools to use next. It is complete enough for correct invocation; only the absence of sibling routing keeps it from a 5.

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 the baseline is 4. The description correctly implies no inputs are needed and instead describes what comes back (screens, buttons, fields), which is the useful semantics here.

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 makes clear this is an instruction-returning tool, not a data-fetch: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That resolves the ambiguity of the noun-only name 'income'. It does not differentiate against close siblings such as ez_lawn_biller_default_income_account, ez_lawn_biller_balances, or ez_lawn_biller_billing_history, so it stops short of a 5.

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?

There is a clear implied workflow: call this to get steps, then execute them with the cotlet_browser_* tools in the Cloud Browser. However, it gives no guidance on when to choose this over sibling tools that also touch income or balances, and no exclusions or prerequisites.

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