Skip to main content
Glama
Sign In
local-docs-mcp

local-docs-mcp

by BitFigther
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_documents

Retrieve a list of documents from the configured local folder, showing relative path, file size, and last modified date.

Instructions

検索対象フォルダ (DOCS_ROOT) 配下のドキュメント一覧を返す。

Returns:
    各ドキュメントの相対パス・サイズ(バイト)・更新日時のリスト。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Without annotations, the description carries full burden. It discloses the function returns a list with specific fields and implies read-only behavior. However, it does not mention order, pagination, or behavior for empty/error states.

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 extremely concise with two sentences, front-loading the purpose and then listing return fields. No superfluous information.

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 description covers the basic purpose and output, it lacks details like whether the listing is recursive, if there are any sorting defaults, or how errors are handled. For a simple list tool, this is adequate but not fully complete.

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

Parameters4/5

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

No parameters exist, so schema coverage is complete. The description adds value by explaining what DOCS_ROOT is and what output is provided, giving context beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a list of documents under DOCS_ROOT, specifying returned fields (relative path, size, bytes, update timestamp). It distinguishes from siblings read_document and search_documents by focusing on broad listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies listing all documents but does not explicitly state when to use this vs. search_documents, nor does it mention any prerequisites or limitations. It lacks explicit when-to-use guidance.

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

Deploy Server

Other Tools