Skip to main content
Glama

Add stock in EZ Lawn Biller

ez_lawn_biller_add_stock
Read-onlyIdempotent

Add 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_add_stock"
  }
}

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 and openWorldHint=false, so the safety profile is covered structurally. The description reinforces this with "opens nothing by itself," which is consistent and helpful, and adds the notable context that no official EZ Lawn Biller API exists so browser automation is required. It does not describe the shape or length of the returned instructions, so it adds moderate value on top of annotations.

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 the action, then the return behavior, then the follow-up tooling — a logical order with no filler sentences. The API-provenance sentence (404 results on /api, /developers, /docs, QuickBooks-only integration) is somewhat verbose for invocation purposes, though it does justify the browser-tool dependency.

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 input schema, no output schema, and rich annotations, the description carries the burden of explaining what comes back, and it does ("step by step (screens, buttons, fields)") plus what to do next. Minor gap: it does not state the response format or that the guidance is text-only, which an agent routing on output would want.

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 baseline is 4 and there is no parameter meaning the description needs to compensate for. The description correctly implies a parameterless, context-only lookup rather than hinting at hidden inputs.

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 gives a specific verb+resource ("Add stock in the user's own EZ Lawn Biller account") and then clarifies the actual mechanic: it "Returns how to do it in EZ Lawn Biller step by step" rather than performing the write itself. That distinction is important and well stated, though it does not differentiate from nearby siblings like ez_lawn_biller_stock or ez_lawn_biller_transfer_stock, leaving the agent to infer which stock tool applies.

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 workflow: call this to get step-by-step instructions, then "do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." It also explains why the browser path is required (no public API). It stops short of explicit exclusions — when to prefer sibling stock tools instead of this guidance tool — which keeps it from a 5.

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