Skip to main content
Glama

lmn_status

Checks whether your Cotlet.dev account, available credits, and LMN connection are ready so you can use LMN tools for estimates, jobs, schedules, timesheets, and billing.

Instructions

Check that your Cotlet.dev account and LMN are ready: account, credits and LMN connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full burden. 'Check' implies a non-mutating read, and the three enumerated areas (account, credits, LMN connection) tell the agent what is inspected, but nothing is said about the result shape, whether failures raise errors versus reporting status, or whether the call has any cost against credits.

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?

A single front-loaded sentence with the readiness verdict first and the checked dimensions after the colon. No filler, no repetition of the tool name, nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only place an agent could learn what comes back; it names the checked dimensions but not the return format (booleans, status strings, error codes) or what a negative result means for next steps. For a zero-parameter read-only tool this is a small but real gap.

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?

The tool takes no parameters, so the schema leaves nothing to explain and the baseline of 4 applies. The description correctly avoids inventing inputs and stays focused on what the zero-argument call reports.

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 uses a specific verb ('Check') with a named resource (Cotlet.dev account and LMN readiness) and enumerates the three things checked: account, credits, and LMN connection. This distinguishes it from the action-oriented siblings (lmn_click, lmn_open, lmn_read), which manipulate a session rather than report readiness, although the description never names that contrast 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: an agent can infer this is a pre-flight check to run before attempting LMN actions, but the description states no explicit when-to-use, no prerequisites, and no conditions under which it should be skipped. There is no reference to any sibling or alternative.

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