Skip to main content
Glama

Stock in EZ Lawn Biller

ez_lawn_biller_stock
Read-onlyIdempotent

Stock 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_stock"
  }
}

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?

Annotations already declare readOnly, idempotent and non-destructive; the description adds the operationally important point that the tool performs no action itself and returns procedural content. It also documents the absence of an official API (404s on /api, /developers, /docs) and that QuickBooks is the only named integration, which justifies the browser-automation route.

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?

Core behavior is front-loaded and the API-research sentence earns its place as justification for the browser-tool handoff. However, the opening clause is ambiguously worded and the description spends a fair amount of text on API archaeology rather than the tool's own output, which weakens the signal-to-noise ratio.

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, no output schema and rich annotations, the remaining burden is describing what comes back — and it does (step-by-step screens, buttons, fields) plus the recommended next step. Only the relationship to the direct 'add_stock' sibling is left unexplained.

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 fully closed, so there is no parameter meaning to add; baseline for a parameterless tool is 4.

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 states a concrete deliverable: it returns step-by-step instructions (screens, buttons, fields) for stocking items in the user's EZ Lawn Biller account, and explicitly clarifies it 'opens nothing by itself'. That distinguishes it from an execution tool like ez_lawn_biller_add_stock by framing it as guidance-only, though the opening clause ('Stock in the user's own EZ Lawn Biller account...') reads like a write action and slightly muddies the verb.

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 clear context for use and a concrete follow-up path: retrieve the steps here, then perform them with the cotlet_browser_* tools in the user's Cloud Browser. It does not explicitly exclude the direct-mutation sibling ez_lawn_biller_add_stock, so an agent must infer which of the two to prefer.

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