Skip to main content
Glama

Run history in EZ Lawn Biller

ez_lawn_biller_run_history
Read-onlyIdempotent

Run history 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_run_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 genuinely new behavioral context: the return value is procedural guidance, not data, and the tool performs no side effects in the account. The note that no public API exists explains why browser automation is the only route, which is useful decision context.

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 core purpose and the follow-up browser-tool chain are front-loaded in the first two sentences, which is good structure. The third sentence, however, spends a lot of words on 404 results, specific URLs and a date for the API investigation, which is background rationale rather than something needed to invoke this tool.

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 no parameters, no output schema and annotations already covering the safety profile, the description supplies what is still missing: the nature of the return value and the exact tools to use next. The API note rounds out completeness by explaining the absence of an API alternative. Only the lack of differentiation from sibling history tools keeps it from being fully complete.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies a parameterless call by describing a fixed deliverable.

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 states the resource (run history) in the user's own EZ Lawn Biller account and, crucially, what the tool actually returns: step-by-step instructions with screens, buttons and fields rather than the data itself. That resolves the ambiguity a name like 'run_history' would otherwise create. It does not distinguish itself from close siblings such as ez_lawn_biller_billing_history, ez_lawn_biller_activity or ez_lawn_biller_activity_log, so the agent has to guess which of the overlapping history tools applies.

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?

The definition gives a concrete workflow: call this first to get the procedure, then execute it with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. It also makes clear this tool opens nothing on its own. It stops short of exclusions, so nothing tells the agent when to prefer a sibling history/activity tool or when this tool is unnecessary.

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