Skip to main content
Glama
deenesjakoruzh
wmt-mobile

LocalNest MCP

by wmt-mobile
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

List Roots

localnest_list_roots
Read-onlyIdempotent

List configured local roots available to the LocalNest MCP server for AI agent codebase access and file discovery.

Instructions

List configured local roots available to this MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • src/mcp/tools/retrieval.js:69-86 (handler)
    Implementation and registration of the localnest_list_roots tool.
    registerJsonTool(
  'localnest_list_roots',
  {
    title: 'List Roots',
    description: 'List configured local roots available to this MCP server.',
    inputSchema: {
      limit: z.number().int().min(1).max(1000).default(100),
      offset: z.number().int().min(0).default(0)
    },
    annotations: {
      readOnlyHint: true,
      destructiveHint: false,
      idempotentHint: true,
      openWorldHint: false
    }
  },
  async ({ limit, offset }) => paginateItems(workspace.listRoots(), limit, offset)
);

Tool Definition Quality

B3.1/5.0
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 that these are 'configured' roots (implying server-side static configuration), but doesn't address caching behavior, pagination defaults, or the relationship between roots and other entities.

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 with no filler. The description is appropriately front-loaded and dense, though minimalism here comes at the cost of parameter documentation.

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?

Given that an output schema exists (covering return values) and annotations declare behavioral safety, the description adequately covers the core concept. However, the complete absence of parameter guidance with 0% schema coverage leaves a significant gap for a tool with optional pagination controls.

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 carries the full burden of explaining parameters but mentions none. While limit/offset are standard pagination patterns, the description should clarify the response_format options ('json' vs 'markdown') and pagination behavior given the lack of schema documentation.

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 verb ('List') and resource ('configured local roots'), distinguishing it from sibling tools like list_projects. However, it doesn't define what constitutes a 'root' in this context (filesystem directory? workspace?), preventing a perfect score.

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 alternatives like localnest_list_projects or localnest_project_tree. No prerequisites, filtering behavior, or exclusion criteria are mentioned.

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