Skip to main content
Glama

Photo evidence in EZ Lawn Biller

ez_lawn_biller_photo_evidence
Read-onlyIdempotent

Photo evidence 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_photo_evidence"
  }
}

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?

Beyond the readOnlyHint/idempotent/non-destructive annotations, the description adds the key behavioral fact that this tool "opens nothing by itself" and only returns instructions, so the agent knows no side effects occur here and must delegate execution elsewhere. It also discloses the integration landscape (no public API; FAQ and manual cite QuickBooks as the only integration), which explains why browser automation is the path.

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?

All the content is relevant, but the middle sentence is tangled: "Returns how to do it... and opens nothing by itself; then do it with the cotlet_browser_* tools" chains two unrelated ideas with an ambiguous pronoun. Splitting return behavior from the execution handoff would make it front-loaded and easier to parse.

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 and no output schema, the description carries the burden of saying what comes back, and it does: step-by-step screens, buttons and fields. The absence of any indication of the response's shape (e.g., plain text vs. structured steps) or length is a minor gap for a zero-input tool.

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. Baseline 4 applies; the description correctly implies no inputs are needed because it just returns a generic procedure.

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?

"Photo evidence in the user's own EZ Lawn Biller account" names a concrete feature area, and "Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)" makes clear the output is procedural instructions rather than an action. It never distinguishes itself from the sibling ez_lawn_biller_minimum_photo_requirements, which sounds closely related, so an agent must infer which photo-related tool to pick.

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 description gives an explicit workflow: call this first for the step-by-step procedure, then execute it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. What is missing is any when-not guidance or a direct comparison against the minimum_photo_requirements sibling.

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