Skip to main content
Glama

ez_lawn_biller_close

Close the signed-in EZ Lawn Biller browser session when work is finished to stop credit usage.

Instructions

Close the EZ Lawn Biller browser session when the work is done, so credits stop running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It usefully reveals the billing consequence ('credits stop running'), which is real behavioral context beyond the schema, but it omits whether the session is irreversibly terminated, what happens to unsaved state, and whether re-opening restores context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, verb-first, with the consequence attached to the action rather than buried. No filler or redundant restatement of the tool name.

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 session-termination tool with no output schema, purpose plus cost rationale is nearly everything an agent needs. The only meaningful gap is the absence of any statement about session state after closing.

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 there is nothing for the description to disambiguate. The empty schema is fully consistent with the described single-purpose action.

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 specific verb (close) and resource (the EZ Lawn Biller browser session), so the action is unambiguous. It does not explicitly contrast itself with siblings like ez_lawn_biller_open or ez_lawn_biller_status, but the resource-level scope makes the distinction inferable.

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?

Provides a timing condition ('when the work is done'), which is genuine when-to-use guidance. It gives no when-not guidance, no mention of what to do if a task fails mid-run, and does not name any alternative tool, leaving alternatives implicit.

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