Skip to main content
Glama

ez_lawn_biller_click

Selects a numbered element on the current EZ Lawn Biller page, letting agents navigate routes, customer records, visit history, and payments after reading available elements.

Instructions

Click a numbered element on the current EZ Lawn Biller page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "ez_lawn_biller_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: not whether the click may navigate away, whether it mutates server-side state, whether element numbering persists or resets after a page change, or what a failure looks like. For an automation tool that can trigger arbitrary page actions, this is a substantial gap.

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?

A single front-loaded sentence with zero filler. Its brevity is efficient, though it comes at the cost of behavioral detail that belongs in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter, no annotations, and no output schema, the definition should explain prerequisites (an open page, a prior read), scope of the click target, and any side effects. None of that is present, so an agent must discover tool behavior empirically.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter's description already says 'Element number from the last read,' so the tool description adds no meaning beyond the schema. Baseline 3 applies for a fully documented single parameter.

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?

States a concrete verb (click) and a concrete target (a numbered element on the current EZ Lawn Biller page), which an agent can distinguish from siblings like type or read. It stops short of naming any sibling or contrasting behavior, so differentiation is inferential.

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?

The phrase 'current EZ Lawn Biller page' and the parameter note 'from the last read' imply a prerequisite: a page must be open and read first, then clicked. That context is only implied — there is no explicit when-to-use, when-not-to-use, or statement of what to do instead (e.g., use type for text entry).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.