Skip to main content
Glama

Bank transfers in EZ Lawn Biller

ez_lawn_biller_bank_transfers
Read-onlyIdempotent

Bank transfers 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_bank_transfers"
  }
}

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 cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is known. The description adds genuinely new behavioral context: the output is procedural instructions rather than data, the tool performs no navigation on its own, and the follow-up action must go through cotlet_browser_* tools. The API-availability note further explains why the browser route is the only path.

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 and the follow-up instruction are front-loaded in the first two clauses. The trailing sentence about 404s on ezlawnbiller.com/api and QuickBooks being the only named integration is longer than necessary and slightly off-topic, though it does justify the browser-based approach.

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 no output schema, the description supplies what an agent needs: what comes back (step-by-step screens/buttons/fields), that nothing is opened, and which tool family performs the actual work. The only shortfall is that it does not state what to do if the user lacks a Cloud Browser session.

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 schema is trivially complete and there is nothing for the description to disambiguate. Baseline for a 0-param tool is 4, and the description correctly avoids inventing parameter semantics.

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 uses a specific verb+resource pair: it returns step-by-step instructions (screens, buttons, fields) for making bank transfers in the user's EZ Lawn Biller account. It is clearly a guidance tool rather than an action tool, which separates it from the many mutating siblings. It never explicitly names a sibling it competes with, so it stops short of a 5.

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 calling context ('from ChatGPT, Claude or any AI agent') and gives an explicit handoff: 'then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' It also says what the tool does not do ('opens nothing by itself'). No explicit when-not-to-use or named alternative guidance tool is given, which keeps it at 4.

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