Skip to main content
Glama

Default Income Account in EZ Lawn Biller

ez_lawn_biller_default_income_account
Read-onlyIdempotent

Default Income Account 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_default_income_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Adds genuinely useful context beyond the annotations: the tool returns instructions rather than acting, and there is no public EZ Lawn Biller API, so automation must go through the browser tools. However, it does not say how the instructions are structured, how long they are, or what happens if the documented screens diverge from the user's live UI, which matters for a read-only guidance tool.

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?

Front-loads the purpose and the key constraint (guidance only, then act via browser tools) in the first two sentences. The closing sentence about the API audit, including a specific future date and 404 results, is tangential detail that dilutes the core message.

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 no output schema, the description usefully explains what the tool returns (screens, buttons, fields) and that it does not act. For a zero-parameter, read-only guidance tool, that covers what an agent needs to invoke and use it correctly.

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; nothing in the description needs to clarify 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?

States the resource (the user's Default Income Account in EZ Lawn Biller) and the specific output: step-by-step instructions covering screens, buttons, and fields. It also distinguishes itself from the cotlet_browser_* tools that actually perform the change. Slightly weakened because the name/title already carries most of the resource identity and the description spends words on an API audit rather than the account-setting concept.

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?

Explicitly frames the tool as guidance-only ('opens nothing by itself') and directs the agent to the cotlet_browser_* tools in the Cloud Browser to actually carry out the steps. This gives a clear usage pattern, though it never states when not to use it or what to do if the user already has a default income account set.

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