Skip to main content
Glama

lmn_read

Reads the current LMN page's text and numbered buttons, links, and fields, optionally limited to one element, so agents can inspect page content before acting.

Instructions

Read the current LMN 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": "lmn_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. "Read" implies no mutation and "current" implies no navigation, but nothing is said about large-page truncation, whether reading scrolls or changes page state, how stable the element numbering is, or what happens with an out-of-range element index.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence: verb, resource, then a compact enumeration of the return contents. No filler, no redundancy.

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-optional-param read tool with no output schema and no annotations, the description usefully sketches the return payload (text plus numbered interactive elements). The remaining gap is that it never explains that the numbering is the handle other tools consume, nor any size/limit behavior, but the core is covered.

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?

The single parameter is fully documented in the schema ("Read only inside this element."), so the schema does the heavy lifting and baseline 3 applies. The description's mention of "numbered buttons, links and fields" weakly connects to the element-index concept but adds no scoping or unit detail beyond the schema.

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?

"Read the current LMN page" names a specific verb and resource, and the colon-clause enumerates what comes back (text, numbered buttons, links, fields). That is enough to separate it from lmn_click/lmn_type, which act on the page rather than report it, though no sibling is named explicitly.

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?

Usage is only implied: reading the current page is naturally the observation step before clicking or typing, and "current" hints it does not navigate (that would be lmn_open). There is no explicit when-to-use, when-not-to-use, or named alternative.

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