Skip to main content
Glama

Brand colour in EZ Lawn Biller

ez_lawn_biller_brand_colour
Read-onlyIdempotent

Brand colour 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_brand_colour"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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; the description corroborates with 'opens nothing by itself' and adds genuinely new context about the return shape (step-by-step screens/buttons/fields) and the absence of a public API. It does not cover verbosity, freshness of the instructions, or what happens if the UI differs from the guide.

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?

Front-loaded with what it returns and what it does not do, followed by the workflow handoff. The closing note on the missing public API is slightly long-winded but earns its place by explaining why browser automation is the only path.

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 instructional tool with no output schema, the description conveys the return type, the fact that it performs no action, and the follow-up tooling needed. Only minor gaps remain, such as whether the steps are version-specific or localized.

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?

With zero parameters and full schema coverage there is nothing to disambiguate, so the baseline applies. The description correctly does not waste space restating a nonexistent input.

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 names a specific resource (brand colour in the user's EZ Lawn Biller account) and states the deliverable: step-by-step instructions covering screens, buttons and fields. It also distinguishes itself from action tools by saying it 'opens nothing by itself' and routing execution to cotlet_browser_* tools. The opening phrase alone is title-like, but the second sentence resolves it.

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?

Clear context: use this to learn how a task is done, then perform it with cotlet_browser_* in the user's Cloud Browser. That implicitly sets it apart from siblings that actually mutate state, though it never explicitly names a sibling or states a 'do not use when' condition.

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