Skip to main content
Glama

Change saved card in EZ Lawn Biller

ez_lawn_biller_change_saved_card
Read-onlyIdempotent

Change saved card 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_change_saved_card"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes beyond the annotations by disclosing the return content (step-by-step screens, buttons, fields) and that the tool has no side effects itself, which explains why readOnlyHint=true on a 'change' tool. It also documents the integration landscape (no public EZ Lawn Biller API as of 11 Nov 2026), justifying the browser-automation 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 handoff are front-loaded in the first sentence, which is well structured. The trailing API-availability sentence is longer than it needs to be and reads as justification padding, though it does explain the browser-tool dependency.

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 zero parameters, no output schema and informative annotations, the description covers what is returned and how to act on it. What remains unstated is whether the described browser steps require an already-open, authenticated 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 baseline is 4 and there is nothing for the description to clarify. The description correctly implies all targeting is derived from the user's own account context rather than arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Change saved card') scoped to 'the user's own EZ Lawn Biller account', and immediately clarifies the tool's real output: step-by-step guidance rather than a mutation. This is enough to distinguish it from siblings like ez_lawn_biller_remove_saved_card without opening any schema.

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?

Explicitly states the workflow: call this to get screens/buttons/fields, then 'do it with the cotlet_browser_* tools', and that it 'opens nothing by itself'. That names the alternative tooling and the handoff condition. It stops short of saying when to skip it (e.g. already-known steps) or preconditions such as an active authenticated browser session.

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