Skip to main content
Glama

Sell a service in EZ Lawn Biller

ez_lawn_biller_sell_a_service
Read-onlyIdempotent

Sell a service 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_sell_a_service"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description explicitly discloses that the tool has zero side effects ('opens nothing by itself'), what it actually returns (screens, buttons, fields), and which tool family must carry out the real action. It even explains the underlying constraint — no public EZ Lawn Biller API, so browser automation is required — which is exactly the kind of context an agent needs to plan a multi-step session.

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 operative content — what it returns, that it does nothing itself, and the cotlet_browser_* follow-up — is front-loaded in the first two sentences. The closing sentence about 404s on /api, /developers and /docs is longer than it needs to be for the justification it provides, but it is not 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?

With no parameters, no output schema and read-only annotations, the description carries all the burden and covers return content and next steps well. The only omission is any statement about prerequisites, such as whether the user's EZ Lawn Biller Cloud Browser session must already be connected before the cotlet_browser_* tools will work.

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 schema has zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter meaning is lost or misrepresented.

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 verb and resource and, crucially, corrects the misleading name: this tool does not sell anything itself, it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That distinction is what separates it from write-oriented siblings like ez_lawn_biller_new_one_time_service or ez_lawn_biller_create_a_draft, though those siblings are never named.

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 a clear two-step workflow: call this to get the click-by-click procedure, then perform it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. That is explicit sequencing guidance rather than implication. It stops short of saying when NOT to use it or naming a sibling tool to use instead for related tasks.

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