Skip to main content
Glama
lanchuske

Pilot MCP

by lanchuske
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

lmcp_state

Check the health of the LMCP environment to diagnose issues with AI agent connections to macOS native apps.

Instructions

LMCP environment health snapshot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:100-100 (registration)
    The tool 'lmcp_state' is registered in the TOOLS array at line 100 with description 'LMCP environment health snapshot'.
    ["lmcp_state", "LMCP environment health snapshot"],
  • server.js:106-110 (handler)
    Generic handler assigned to all tools including lmcp_state. It returns a stub message indicating this is an inspection stub and directing to install Local MCP.
    for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
  }));
}
  • server.js:107-107 (schema)
    Empty schema object '{}' is passed as the input schema for all tools including lmcp_state, meaning no parameters are accepted.
    server.tool(name, desc, {}, async () => ({

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

The description does not disclose behavioral traits such as read-only nature, side effects, or authentication requirements. Annotations are absent, so the description must cover these, but it only implies a read operation with 'snapshot' without explicit confirmation.

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?

The description is very concise, using only four words. It front-loads the key information. However, it may be overly terse at the expense of completeness.

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?

Given no parameters, no output schema, and no annotations, the description should provide more context about what a 'health snapshot' entails, what LMCP means, and what the output looks like. The current description is insufficient for an agent to invoke the tool confidently.

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?

There are no parameters, so the input schema provides full coverage. The description adds no extra meaning but also does not need to. Baseline score of 3 is appropriate given 100% schema coverage and no parameters.

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 clearly states it provides a 'health snapshot' of the 'LMCP environment', indicating a specific resource and action. It distinguishes itself from sibling tools which are unrelated (calendar, notes, email, etc.). However, the acronym LMCP is not explained, slightly reducing clarity.

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?

No guidance is provided on when or why to use this tool versus alternatives. The description lacks context on typical usage scenarios or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server