Skip to main content
Glama

Health

localnest_health
Read-onlyIdempotent

Check runtime health status for fast smoke testing of the local-first MCP server, returning a compact summary in JSON or Markdown format.

Instructions

Return a compact runtime health summary for fast smoke checks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • The handler for the 'localnest_health' tool, which aggregates server status and background health reports.
    async () => {
      const status = await buildServerStatus();
      return {
        name: status.name,
        version: status.version,
        mode: status.mode,
        health: status.health,
        roots_count: Array.isArray(status.roots) ? status.roots.length : 0,
        update_recommendation: status.updates?.recommendation || 'up_to_date',
        background_health: getLastHealthReport?.() ?? null
      };
    }
  • Registration of the 'localnest_health' tool within the registerCoreTools function.
    registerJsonTool(
      'localnest_health',
      {
        title: 'Health',
        description: 'Return a compact runtime health summary for fast smoke checks.',
        inputSchema: {},
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false
        }
      },
      async () => {
        const status = await buildServerStatus();
        return {
          name: status.name,
          version: status.version,
          mode: status.mode,
          health: status.health,
          roots_count: Array.isArray(status.roots) ? status.roots.length : 0,
          update_recommendation: status.updates?.recommendation || 'up_to_date',
          background_health: getLastHealthReport?.() ?? null
        };
      }
    );
Behavior4/5

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

Annotations already establish read-only, idempotent safety. The description adds valuable behavioral context not in annotations: 'compact' signals minimal payload size and 'fast' implies low latency, helping the agent understand performance characteristics.

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?

Nine words, front-loaded with the verb 'Return', zero redundancy. Every modifier ('compact', 'runtime', 'fast', 'smoke checks') adds distinct value about scope or performance.

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?

Adequate for a simple health endpoint with output schema present and clear annotations, but the undocumented parameter leaves a gap. Given the tool's low complexity, the description covers the essential behavioral contract despite missing parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate but fails to mention the response_format parameter at all. While the enum values are self-documenting in the schema, the description provides no guidance on when to use markdown vs json or what each format contains.

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 the tool returns a 'compact runtime health summary' with specific scope ('fast smoke checks'). It effectively distinguishes from sibling status tools like localnest_server_status by emphasizing compactness and speed, though it doesn't explicitly name alternatives.

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?

The phrase 'for fast smoke checks' provides clear context about when to use this tool (quick health validation). However, it lacks explicit exclusions or guidance on when to use more detailed status tools instead.

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/wmt-mobile/localnest'

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