Skip to main content
Glama

Geographic service areas in EZ Lawn Biller

ez_lawn_biller_geographic_service_areas
Read-onlyIdempotent

Geographic service areas 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_geographic_service_areas"
  }
}

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?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds non-obvious behavior: 'opens nothing by itself' — the tool returns text and performs no navigation or mutation, deferring action to browser tools. It also discloses the absence of a public API, explaining why the guide-and-browse path exists. Return content is described at a coarse level (step-by-step screens/buttons/fields).

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 core behavior (returns a guide, acts via browser tools) is front-loaded in the first two sentences. The closing API-availability sentence is longer than needed and somewhat tangential, but it does justify the tool's existence, so it earns most of its space.

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 tool with no output schema, the description covers what comes back (a step-by-step procedure), what does not happen (no automatic opening or changes), and the follow-up action. The only missing piece is granularity about how the steps are structured for the agent to consume.

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 compensate for undocumented 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 names a specific resource (geographic service areas) in the user's own EZ Lawn Biller account and states what the tool returns: step-by-step instructions (screens, buttons, fields) rather than data. The verb is diffuse ('returns how to do it'), but an agent can tell this is a guidance tool rather than a data or mutation tool.

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 states the workflow explicitly: this tool returns instructions, then the agent should act using cotlet_browser_* tools in the Cloud Browser. That is a real when-to-use directive. It does not exclude or compare against the sibling ez_lawn_biller_* tools, so the guidance stops short of full routing.

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