Skip to main content
Glama

Usage Guide

localnest_usage_guide
Read-onlyIdempotent

Get best-practice guidance for using LocalNest MCP to access codebases locally with file discovery, search, and project introspection while keeping data on your machine.

Instructions

Return concise best-practice guidance for users and AI agents using this MCP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • Implementation of the buildUsageGuide function, which provides the response for the localnest_usage_guide tool.
    export function buildUsageGuide() {
      return {
        quickstart: [
          '1. Run localnest_server_status to confirm runtime health and active roots.',
          '2. Use localnest_search_files to find a module, feature, or folder by name.',
          '3. Use localnest_search_code for exact symbols, imports, and error strings.',
          '4. Use localnest_read_file only after narrowing the target.'
        ],
        release_debug: [
          'If retrieval looks empty, validate project_path first, then retry with a broader query.',
          'If runtime looks degraded, inspect server_status.health and updates before deeper debugging.',
          'Use localnest_update_status to see whether cached version data is stale or actionable.'
        ],
        for_users: [
          'Run localnest_list_roots first to verify active roots.',
          'Use localnest_list_projects to discover projects under a root.',
          'Run localnest_index_project for your active project/root before semantic search.',
          'Use localnest_search_hybrid for low-noise retrieval.',
          'Use localnest_read_file for targeted context windows.',
          'Use localnest_task_context for one-call runtime + memory context before non-trivial work.',
          'Use localnest_capture_outcome for one-call outcome capture after meaningful work.',
          'Use localnest_memory_status to verify whether local memory is enabled and supported on this runtime.',
          'Use localnest_memory_capture_event to preserve durable project decisions and preferences after meaningful work.',
          'Use localnest_update_status when you need to verify whether a newer stable version is available.'
        ],
  • Registration of the localnest_usage_guide tool in the core tools registry.
    registerJsonTool(
      'localnest_usage_guide',
      {
        title: 'Usage Guide',
        description: 'Return concise best-practice guidance for users and AI agents using this MCP.',
        inputSchema: {},
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false
        }
      },
      async () => buildUsageGuide()
    );
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context that the returned content is 'best-practice guidance' (documentation/help content) rather than code, status, or raw data. Does not mention caching behavior or response size expectations.

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?

Single sentence, front-loaded with the action verb 'Return'. No filler words or redundant phrases. Efficiently conveys the tool's purpose without verbosity.

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?

Appropriately complete for a simple documentation tool that has an output schema (which handles return value documentation). Annotations cover behavioral safety. Only gap is the undocumented response_format parameter, which prevents a score of 5.

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?

Schema has 0% description coverage for the single parameter (response_format). The description fails to compensate by explaining the parameter's purpose, the difference between 'json' and 'markdown' formats, or that it defaults to 'json'. The parameter name is somewhat self-explanatory, but explicit guidance is missing.

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 specific verb 'Return' and clear resource 'best-practice guidance', distinguishing this from operational siblings like localnest_search_code or localnest_memory_store. It clearly identifies the audience (users and AI agents) and scope (this MCP). Minor gap: doesn't specify what topics the guidance covers (e.g., tool selection, query patterns).

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 explicit when-to-use or when-not-to-use guidance is provided. The description doesn't indicate whether this should be called at session start, when confused, or as an alternative to localnest_server_status. Users must infer usage from the name alone.

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