Skip to main content
Glama

ez_lawn_biller_read

Reads the current EZ Lawn Biller page to return text and numbered buttons, links, and fields, optionally within one element, so agents can inspect page state before acting.

Instructions

Read the current EZ Lawn Biller page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

With no annotations supplied, the description must carry the full behavioral burden. It does disclose the return shape (text, numbered buttons, links, fields), which is genuinely useful for a read tool, but says nothing about whether it is strictly non-mutating, how numbering stays stable across calls, or how long pages are truncated.

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?

One short sentence, front-loaded with the verb and resource. The trailing list of yielded items is slightly loose in punctuation but every clause adds information about the output.

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 read tool with no output schema and no annotations, the definition covers the essential behavior: what page it targets and what the result contains. Missing only secondary details like truncation and numbering continuity, which an agent can discover at call time.

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?

With a single optional parameter at 100% schema coverage, the schema already explains "element: read only inside this element." The description correctly stays out of the way and describes what the read returns instead of redundantly restating the 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 specific verb ("Read") and a specific resource ("the current EZ Lawn Biller page"), then enumerates what it yields: text, numbered buttons, links, and fields. That is enough to distinguish it from the click/type/open siblings without opening another schema, though no sibling is named.

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 "current" implies the page must already be open (i.e., after ez_lawn_biller_open), which is useful implied guidance. However, it never states when to choose this versus the status/guide tools, nor any precondition or exclusion explicitly.

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