Skip to main content
Glama

ez_lawn_biller_status

Verify that your Cotlet.dev account, credits, and EZ Lawn Biller connection are ready before running lawn billing tasks.

Instructions

Check that your Cotlet.dev account and EZ Lawn Biller are ready: account, credits and EZ Lawn Biller connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/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 burden. It lists the three things inspected (account, credits, connection), which is useful, but says nothing about whether the call is read-only, what happens on a failed check, whether it touches the network or consumes credits to verify them, or how failures are surfaced.

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 the verb first, which is appropriate for a zero-parameter status tool. It is slightly redundant, repeating 'account' and 'EZ Lawn Biller' within the same clause, but no sentence is wasted.

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

Completeness3/5

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

With no annotations and no output schema, the description is the only source of information about results, and it does not say what a successful or failing response looks like (per-item pass/fail? a single boolean? an error message?). It explains what is checked but not how the agent should interpret the answer.

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 baseline of 4 applies. No parameter-level meaning is missing.

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 clear verb ('Check ... are ready') and a specific resource set: Cotlet.dev account, credits, and the EZ Lawn Biller connection. That makes it distinguishable from the interaction siblings (click, close, open, read, type), which are action tools, though it never explicitly frames itself as a pre-flight check relative to them.

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 word 'ready' implies this is a precondition/diagnostic call, but the description never states when to call it, when not to, or that it should precede the other EZ Lawn Biller tools. An agent must infer the sequencing from the word 'ready' alone.

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