Skip to main content
Glama

Sales Tax in EZ Lawn Biller

ez_lawn_biller_sales_tax
Read-onlyIdempotent

Sales Tax 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_sales_tax"
  }
}

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?

With readOnlyHint/openWorldHint=false/idempotent already declared, the description adds real value by clarifying that the tool only returns guidance and performs no action itself, and that execution requires the separate cotlet_browser_* tools. The API-availability note (404s on /api, /developers, /docs; only QuickBooks integration) explains why browser automation is the path, which is meaningful context an agent cannot get from annotations.

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?

Purpose and the critical 'opens nothing by itself' constraint are front-loaded, and the follow-up routing is compact. Minor waste in 'from ChatGPT, Claude or any AI agent,' which adds no decision-relevant information, and the dated API paragraph is dense but earns its place by justifying the browser route.

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 parameterless, read-only, closed-world guidance tool with no output schema, the definition covers what is returned (step-by-step screens/buttons/fields), what it does not do (no execution), and what to use next. The only gap is whether the returned steps are static generic instructions or tailored to the user's account specifics.

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 and the schema is an empty closed object, so there is no parameter semantics to explain. Baseline 4 applies; nothing in the description misrepresents the 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?

The description states a specific outcome: it returns step-by-step instructions (screens, buttons, fields) for handling sales tax in EZ Lawn Biller, and explicitly says it 'opens nothing by itself.' That distinguishes it from the numerous mutation siblings. The leading phrase 'Sales Tax in the user's own EZ Lawn Biller account' largely restates the tool name, so the real purpose only lands in the second sentence.

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 clearly routes the agent: call this to obtain the procedure, then execute it with the cotlet_browser_* tools in the user's Cloud Browser. That is an explicit when-to-use plus a named alternative for the actual execution. It stops short of stating when not to use it (e.g., for other EZ Lawn Biller topics or when the agent already knows the flow).

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