Skip to main content
Glama

Server Status

localnest_server_status
Read-onlyIdempotent

Check runtime status and active configuration of the LocalNest MCP server to monitor local-first AI agent operations and ensure safe codebase access functionality.

Instructions

Return runtime status and active configuration summary for this MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • Registration of localnest_server_status tool.
    registerJsonTool(
      'localnest_server_status',
      {
        title: 'Server Status',
        description: 'Return runtime status and active configuration summary for this MCP server.',
        inputSchema: {},
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false
        }
      },
      async () => buildServerStatus()
    );
  • Implementation of buildServerStatus which is called by localnest_server_status.
    return async function buildServerStatus() {
      const indexStatus = vectorIndex?.getStatus?.() || null;
      const activeIndexBackend = getActiveIndexBackend();
      const memoryStatus = await memory.getStatus();
      const updateStatus = updates.getCachedStatus
        ? updates.getCachedStatus()
        : await updates.getStatus({ force: false });
    
      return {
        name: serverName,
        version: serverVersion,
        mode: runtime.mcpMode,
        roots: workspace.listRoots(),
        has_ripgrep: runtime.hasRipgrep,
        health: buildHealthSummary({
          runtime,
          memoryStatus,
          indexStatus,
          activeIndexBackend
        }),
        memory: buildMemorySummary(memoryStatus),
        search: {
          auto_project_split: runtime.autoProjectSplit,
          max_auto_projects: runtime.maxAutoProjects,
          force_split_children: runtime.forceSplitChildren,
          rg_timeout_ms: runtime.rgTimeoutMs
        },
        vector_index: {
          backend: activeIndexBackend,
          requested_backend: runtime.indexBackend,
          index_path: runtime.vectorIndexPath,
          db_path: runtime.sqliteDbPath,
          chunk_lines: runtime.vectorChunkLines,
          chunk_overlap: runtime.vectorChunkOverlap,
          max_terms_per_chunk: runtime.vectorMaxTermsPerChunk,
          max_indexed_files: runtime.vectorMaxIndexedFiles,
          embedding_provider: runtime.embeddingProvider,
          embedding_model: runtime.embeddingModel,
          embedding_cache_dir: runtime.embeddingCacheDir,
          embedding_cache_status: runtime.embeddingCacheStatus || null,
          embedding_dimensions: runtime.embeddingDimensions,
          reranker_provider: runtime.rerankerProvider,
          reranker_model: runtime.rerankerModel,
          reranker_cache_dir: runtime.rerankerCacheDir,
          reranker_cache_status: runtime.rerankerCacheStatus || null,
          diagnostics: {
            sqlite_vec_loaded: indexStatus?.sqlite_vec_loaded ?? indexStatus?.sqlite_vec_extension?.loaded ?? null,
            sqlite_vec_extension_path: indexStatus?.sqlite_vec_extension?.path || runtime.sqliteVecExtensionPath || '',
            sqlite_vec_extension_configured: Boolean(indexStatus?.sqlite_vec_extension?.configured || runtime.sqliteVecExtensionPath),
            sqlite_vec_table_ready: indexStatus?.sqlite_vec_table_ready ?? null,
            index_sweep_interval_minutes: runtime.indexSweepIntervalMinutes
          },
          upgrade_recommended: indexStatus?.upgrade_recommended || false,
          upgrade_reason: indexStatus?.upgrade_reason || null
        },
        updates: updateStatus
      };
    };
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds semantic context by specifying what is returned (runtime status and configuration), but does not elaborate on caching, performance characteristics, or the nature of the configuration data.

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?

The description is a single, efficient sentence that is front-loaded with the verb. There is no redundant or wasted text.

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?

While the existence of an output schema reduces the need to describe return values, the complete lack of parameter documentation (0% schema coverage) in either schema or description leaves a gap. The tool is simple but not fully specified.

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 fails to compensate for the undocumented 'response_format' parameter. It does not explain the enum values ('json', 'markdown') or their implications for consuming the output.

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 ('Return') and clearly identifies the resource ('runtime status and active configuration summary'). It scopes the tool to 'this MCP server,' but could better differentiate from siblings like 'localnest_health' or 'localnest_index_status'.

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?

The description provides no guidance on when to use this tool versus the numerous sibling status tools (health, index_status, memory_status, etc.). It lacks explicit when-to-use criteria or exclusions.

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