Skip to main content
Glama

lmn_open

Opens an LMN page in your signed-in Cloud Browser, defaulting to https://my.golmn.com, so you can review landscaping estimates, schedules, timesheets, and invoices.

Instructions

Open a LMN page in your signed-in Cloud Browser (default https://my.golmn.com) to work with review landscaping estimates, schedules, timesheets and invoices.

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": "lmn_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://my.golmn.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that the browser is 'signed-in' (session/auth context already established, no login step needed), but says nothing about whether it navigates the current tab, what happens on an invalid URL, or what the call returns.

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 front-loaded sentence with the action and destination first and the example workflows trailing. The trailing list of business objects is slightly promotional but still orienting; nothing is wasteful enough to cut.

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 navigation tool with no output schema, the definition covers the action, the default target, and the authenticated context. The only real gap is the post-open relationship to lmn_read/lmn_status, which an agent must infer.

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 coverage is 100% and the single optional url parameter is fully documented in the schema, including the same default. The description repeats that default rather than adding new meaning, so baseline 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?

Names a specific verb and resource: 'Open a LMN page in your signed-in Cloud Browser', with the default destination inlined. That distinguishes it from siblings like lmn_click, lmn_type and lmn_read, though the distinction is implied by the verb rather than stated.

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 mention of reviewing estimates, schedules, timesheets and invoices implies this is the entry point for navigating to a page before acting on it, but there is no explicit when-to-use, no statement that it should precede lmn_read/lmn_click, and no exclusions.

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