Skip to main content
Glama

Schedule jobs in EZ Lawn Biller

ez_lawn_biller_schedule_jobs
Read-onlyIdempotent

Schedule jobs 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_schedule_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces the no-side-effect profile with 'opens nothing by itself.' It adds genuinely beyond the annotations by saying the return value is procedural guidance covering screens, buttons, and fields, which matters since there is no output schema. The API-research note (404s on /api, /developers, /docs; QuickBooks the only named integration) also 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?

The behavioral core ('returns steps, opens nothing, then use cotlet_browser_*') is front-loaded and useful, but the opening 'from ChatGPT, Claude or any AI agent' is marketing padding and the API-availability paragraph is long and oddly dated (11 Nov 2026). Both could be compressed to a clause without losing decision-relevant information.

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 no-parameter, read-only guidance tool with no output schema, the description covers what it does, what it returns, that it has no side effects, and how to execute the result. Only a brief note on the shape of the returned steps (text/markdown, granularity) is missing, which is a minor gap rather than a blocker.

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 the schema is a closed empty object, so there is nothing for the description to disambiguate; the baseline for a 0-param tool applies. The description doesn't wrongly imply any input, and the mention of the user's own account correctly signals that scoping comes from the session, not from arguments.

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 makes the actual function explicit: it returns step-by-step instructions (screens, buttons, fields) for scheduling jobs and 'opens nothing by itself,' which corrects the impression created by the name. That is a specific verb+resource plus a scope statement. It does not differentiate itself from the many sibling 'schedule' tools (ez_lawn_biller_schedule, ez_lawn_biller_work_schedule, ez_lawn_biller_daily_schedule), leaving the agent to infer that those are data reads while this is a how-to guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear follow-up path: act on the returned steps with the cotlet_browser_* tools inside the user's EZ Lawn Biller Cloud Browser, which is real context for using the output. However, there is no explicit when-to-use/when-not statement and no naming of the sibling schedule tools the agent should choose instead when it wants actual schedule data rather than guidance.

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