Skip to main content
Glama

ez_lawn_biller_guide

Guides you through EZ Lawn Biller tasks: plan lawn routes, record payments, review past-due accounts, and locate the sign-in link. Call first for task-specific directions.

Instructions

How to work in EZ Lawn Biller (plan lawn routes, record payments and review past-due accounts): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in EZ Lawn Biller, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does convey the substance of the response (screens and a sign-in link), which implies an informational, non-mutating tool, but it never states outright that the call has no side effects or what form the output takes. For a low-risk guide that implication may be sufficient, but it is inference rather than disclosure.

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 short sentences with no padding, and the topical content is front-loaded in the parenthetical. Placing 'Call this first' at the end is a deliberate call-to-action rather than wasted wording, though it would be marginally stronger at the front.

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 one-parameter, no-output-schema guide tool, the description covers purpose, content, and invocation order. The only gap is that it does not say what the returned guide looks like or whether the task argument changes the answer, which matters slightly given the free-form parameter.

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?

There is one optional parameter with 100% schema description coverage, so the baseline is 3. The description does not elaborate on what the 'task' string should contain or how it shapes the response, leaving the schema to do all the work.

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 the resource (a guide to EZ Lawn Biller) and enumerates the concrete content it covers: screens, route planning, payment recording, past-due account review, and the sign-in link. That is enough to distinguish it from the action siblings (open, click, type, read, status), which operate the app rather than explain it. It stops short of a crisp verb+resource phrasing like 'Return an orientation guide for...', which is why it is a 4 rather than a 5.

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?

'Call this first' gives explicit ordering guidance that an agent can act on immediately. What is missing is any when-not condition or named alternative for the case where the agent already knows the app, but for a single entry-point guide tool the sequencing instruction covers the main decision.

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