Skip to main content
Glama

Per-service rates in EZ Lawn Biller

ez_lawn_biller_per_service_rates
Read-onlyIdempotent

Per-service rates 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_per_service_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it explains the tool returns instructions rather than performing work, that it opens nothing itself, and that no public API exists so browser automation is required. The lack of any note on output shape or length is the only gap.

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 scope statement is front-loaded, which is good, but the trailing API-research note is verbose and date-stamped ('/api, /developers and /docs returned 404 on 11 Nov 2026'), and the QuickBooks/FAQ detail reads as provenance logging rather than invocation guidance. The core actionable content could be stated in half the words.

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 informational tool with no output schema, the description covers what it returns, what it does not do, and what the agent should do next. Nothing an agent needs in order to call it correctly is missing, though a brief indication of response format would make it fully self-contained.

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 properties, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies a parameterless lookup and does not invent 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 ('Per-service rates in the user's own EZ Lawn Biller account') and states the output form: step-by-step instructions with screens, buttons and fields. It also makes clear this is a guidance/knowledge tool rather than a mutating action, which distinguishes it from siblings like ez_lawn_biller_edit_service_type. It stops short of a crisp single verb ('returns how to do it' is a bit roundabout), keeping it out of the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete follow-on workflow ('then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser') and a clear non-behavior ('opens nothing by itself'). However, there is no explicit statement of when to choose this over adjacent siblings such as ez_lawn_biller_service_catalog or ez_lawn_biller_material_cost_per_service — the selection condition is only implied.

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