Skip to main content
Glama

Credits in EZ Lawn Biller

ez_lawn_biller_credits
Read-onlyIdempotent

Credits 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_credits"
  }
}

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, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context: it produces step-by-step screens/buttons/fields, performs no action itself, and requires a separate browser tool to execute, plus it explains why no API path exists. That is real value beyond the annotations.

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 workflow, no-op guarantee, and API-unavailability note each earn their place, but the opening sentence is a noun fragment ('Credits in the user's own EZ Lawn Biller account from ChatGPT, Claude or any AI agent') that delays the actual function. Front-loading the 'returns step-by-step instructions' clause would improve it.

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 guidance tool with full annotation coverage and no output schema, the description covers what it returns, what it does not do, and how to complete the task afterward. The only gap is the lack of a clear trigger condition for choosing it over siblings.

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 there is nothing for the description to disambiguate; a baseline of 4 applies. The absence of arguments is consistent with the stated behavior of returning static guidance.

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 makes the resource ('Credits in the user's own EZ Lawn Biller account') and the actual operation ('returns how to do it step by step') explicit, and crucially distinguishes this from an acting tool by stating it 'opens nothing by itself.' The opening fragment is grammatically loose, but an agent can still tell this is a guidance/instruction-returning tool rather than a 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 Guidelines3/5

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

It gives one concrete follow-up path: use the cotlet_browser_* tools in the user's Cloud Browser after reading the steps. However, it never states when to prefer this over the numerous ez_lawn_biller_* siblings or what preconditions (e.g., an active Cloud Browser session) must hold, so usage 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