Skip to main content
Glama

list_docs

Retrieve a list of documents stored in the Docs-MCP server to efficiently manage and access user-configured files for search and reference purposes.

Instructions

所持しているドキュメントの一覧を取得

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_docs': decorated with @mcp.tool(), provides docstring, and delegates to DocumentManager.list_documents() to list available documents.
    @mcp.tool()
    async def list_docs() -> str:
        """所持しているドキュメントの一覧を取得"""
        return doc_manager.list_documents()
  • Core logic for listing documents: iterates over loaded docs_content, appends path and metadata description, joins into a string.
    def list_documents(self) -> str:
        """ドキュメント一覧を返す"""
        result = []
        for path in sorted(self.docs_content.keys()):
            description = self.docs_metadata.get(path, "")
            if description:
                result.append(f"{path} - {description}")
            else:
                result.append(path)
        return "\n".join(result)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it retrieves a list but doesn't describe what format the list returns (titles, IDs, metadata), whether there's pagination, authentication requirements, rate limits, or what 'owned documents' means in context. This leaves significant behavioral gaps for the agent.

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 Japanese sentence that directly states the tool's purpose without any wasted words. It's appropriately sized for a simple list retrieval tool and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what information the list contains (document titles, IDs, metadata), the format of the return value, whether there are limitations (max results, pagination), or authentication context. Given the lack of structured data, the description should provide more complete operational context.

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?

The tool has 0 parameters with 100% schema description coverage (empty schema). The description appropriately doesn't discuss parameters since none exist. A baseline of 4 is appropriate for parameterless tools where the description focuses on purpose rather than parameter 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 action ('取得' - get/retrieve) and resource ('所持しているドキュメントの一覧' - list of owned documents), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like get_doc (single document retrieval) or grep_docs (content search), which would be needed for 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. There's no mention of when to prefer list_docs over get_doc (for single document retrieval), grep_docs (for content search), or semantic_search (for semantic matching). The agent must infer usage from tool names 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

Related 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/herring101/docs-mcp'

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