Skip to main content
Glama

Notice templates in EZ Lawn Biller

ez_lawn_biller_notice_templates
Read-onlyIdempotent

Notice templates 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_notice_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description still adds meaningful behavior: the tool performs no action itself, returns screen/button/field level instructions, and must be followed by browser tools. It also discloses integration reality (no public API; QuickBooks named as the only integration), which keeps the agent from attempting an API 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?

Two sentences, front-loaded with what is returned and the 'opens nothing by itself' caveat, then the handoff to browser tools. The trailing API-availability note is somewhat verbose with dated 404 evidence, but it earns its place by ruling out a direct-API route.

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 guidance tool with no output schema, the description covers what is returned, that nothing is mutated, and what to do next. Return formatting or how the step list is structured is left implicit, which is a minor gap rather than a blocking one.

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 schema imposes no burden and a baseline of 4 applies. The description introduces no phantom inputs and correctly frames the response as procedural instructions rather than a data query.

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

Purpose3/5

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

The second sentence makes clear this is a guidance tool that 'returns how to do it ... step by step' and 'opens nothing by itself', which is a real behavior statement. But the leading fragment 'Notice templates in the user's own EZ Lawn Biller account' never says whether it lists notice templates or explains how to work with them, and nothing distinguishes it from sibling template tools such as ez_lawn_biller_templates or ez_lawn_biller_custom_templates.

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?

There is explicit follow-through guidance: after reading the steps, act with the cotlet_browser_* tools in the Cloud Browser, which is a genuine routing instruction. There is no when-to-use versus the other template siblings (custom_templates, templates, archive_template), so the agent must guess which template tool to pick.

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