Skip to main content
Glama

Minimum photo requirements in EZ Lawn Biller

ez_lawn_biller_minimum_photo_requirements
Read-onlyIdempotent

Minimum photo requirements 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_minimum_photo_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is known. The description adds genuine context beyond them — that this is an informational how-to that performs no navigation and is followed by browser-tool execution — plus the finding that no public EZ Lawn Biller API exists, which explains why browser automation is required. It does not describe output size or format beyond "step by step (screens, buttons, fields)."

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?

Three sentences, front-loaded with what is returned and what the tool does not do. Minor waste: "from ChatGPT, Claude or any AI agent" is filler, and the closing API-404 footnote, while relevant to why browser tools are needed, is dense and only indirectly about 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?

For a zero-parameter, read-only, output-schema-less guidance tool, the description covers what is returned, that no side effects occur, and what to do next. The only shortfall is that the shape of the returned steps (a single text block versus structured sections) is left implicit.

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 and has no schema fields to interpret, so there is no parameter meaning the description needs to supply. By the zero-parameter baseline this is adequate.

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 identifies the resource (minimum photo requirements in the user's EZ Lawn Biller account) and, crucially, states the operation: "Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)." That distinguishes it from a data-reading tool, though the opening noun phrase restates the title before the verb appears, and it never contrasts itself with the sibling photo_evidence tool.

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 gives a clear context of use and a concrete follow-up path: use the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser after reading the steps, and it warns that this tool "opens nothing by itself." No explicit when-not-to-use or exclusion against sibling tools is given, but the sequencing guidance is unusually actionable.

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