Skip to main content
Glama

Connect to QuickBooks in EZ Lawn Biller

ez_lawn_biller_connect_to_quickbooks
Read-onlyIdempotent

Connect to QuickBooks 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_connect_to_quickbooks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral value beyond them: it states the tool returns instructions rather than performing the action ('opens nothing by itself') and explains there is no public EZ Lawn Biller API, which steers the agent away from attempting direct API calls. It stops short of describing output format or handling of an already-connected account.

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 and follow-up path are front-loaded in the first two sentences, which is good. The trailing sentence about ezlawnbiller.com/api, /developers and /docs returning 404 is verbose and includes a specific date and URL list that costs more space than it earns, and the 'from ChatGPT, Claude or any AI agent' clause is filler.

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 guide tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields), that it changes nothing, and how to act on the result via the browser tools. The only gap is behavior when the user is already connected to QuickBooks, which is not addressed.

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 parameters, so there is no parameter meaning for the description to supply; the baseline for a parameterless tool applies. The description correctly implies the tool is invoked with no arguments and returns user-specific guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource and action (connect QuickBooks inside EZ Lawn Biller) and immediately clarifies the actual output: 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields).' It also explicitly negates the naive reading of the tool name by stating it 'opens nothing by itself', so an agent cannot mistake this for a mutation of the user's account.

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 clear when-to-use context and a concrete follow-up path: do the connection 'with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' It does not name alternatives or exclusions (for example the disconnect sibling or what to do if the account is already linked), but the positive routing guidance is unambiguous.

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