Skip to main content
Glama

lmn_guide

Learn how to sign in to LMN and navigate its screens to review landscaping estimates, schedules, timesheets, and invoices; call this first.

Instructions

How to work in LMN (review landscaping estimates, schedules, timesheets and invoices): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in LMN, in your words.

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, the description carries the whole burden. It hints at content (screens, sign-in link) but never says what is actually returned — prose steps, links, UI selectors? — nor confirms the tool only reads and takes no action on the account. For a safe-looking help tool that is a modest but real gap.

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?

Two short, front-loaded fragments with no waste, and the action directive ('Call this first') lands last for emphasis. The parenthetical list of covered objects is long but earns its place by scoping the guide.

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, no-output-schema primer this is close to sufficient: what it covers and when to call it are both stated. Only the shape of the response and the read-only, non-mutating nature of the tool are left implicit.

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% and the single 'task' parameter is already documented as 'What you want done in LMN, in your words.' The description never references the parameter, so it adds nothing beyond the schema; 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?

The description states a specific resource (guidance for working in LMN) and enumerates the covered domain objects: estimates, schedules, timesheets and invoices. It is clearly separable from the sibling UI-action tools (lmn_click, lmn_open, lmn_read), though it lacks an explicit verb such as 'returns' or 'explains'.

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

Usage Guidelines4/5

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

'Call this first' gives an explicit sequencing instruction that no sibling provides, which is exactly the routing signal an agent needs for an orientation tool. It stops short of saying when the guide is unnecessary (e.g. for an agent already mid-task), so it is not a full when/when-not statement.

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