Skip to main content
Glama

lmn_click

Click a numbered element on the current LMN page to navigate landscaping estimates, jobs, schedules, and billing screens using element numbers from the last page read.

Instructions

Click a numbered element on the current LMN 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": "lmn_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden and it does not. It never says whether clicking navigates, submits, mutates state, or what happens if the element number is stale or invalid, nor whether the returned element numbering changes afterward.

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 no filler or redundancy. Brevity is appropriate to the surface form, though some of that space could have been spent on behavioral detail.

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?

For an interactive click tool with no annotations and no output schema, the definition is too thin. An agent cannot tell from the description whether the click triggers navigation, whether the page's element numbering is invalidated, or what the tool returns, all of which are essential to invoking it correctly.

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 description coverage is 100%, with the element parameter documented as 'Element number from the last read'. The description's 'numbered element' adds only a minor restatement, so the schema is doing the semantic work and the baseline of 3 applies.

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 (click) and a specific resource (a numbered element on the current LMN page), which is enough to separate it from read/type/open/close siblings. It stops short of naming any alternative or clarifying the relationship to lmn_read, which supplies the numbering.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of clicking versus typing into an element. The phrase 'current LMN page' hints that a page must already be open, but the prerequisite of having just read the page is only implied through the schema.

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