QiitaDrive is a PowerShell module wrapping Qiita API access via a virtual filesystem. Tool definitions are inferred from cmdlet source files rather than explicitly registered in an MCP manifest. Input schemas are partially visible but lack complete type information and descriptions for many parameters. Descriptions exist but are brief (10-50 chars) and lack actionable context for LLM selection. No output schemas documented. No error handling guidance. This is a PowerShell cmdlet module, not an MCP server, transport mechanism is unknown/unclear.

• Create an explicit MCP server manifest (e.g., server.json or mcp.yaml) that registers all 5 tools with canonical names, full descriptions (50-200 chars), complete input schemas with type and description for every parameter, and documented output schemas.
• Expand tool descriptions to 50-200 characters, explaining WHAT the tool does, WHEN to use it vs similar tools, and what it returns. E.g., 'Get-QiitaItem: Fetch a Qiita article by ID or URL, returning the full body text and metadata. Use this to read article content; use Get-QiitaComment to fetch discussion threads.'
• Move OAuth credentials (Token, ClientSecret) from New-QiitaDrive parameters to server-side environment variables or a secure config file. Document how to set QIITA_TOKEN and QIITA_CLIENT_SECRET before starting the server.
• Document output schemas for each tool. E.g., Get-QiitaItem returns {item_id: string, title: string, body: string, author_id: string, created_at: ISO8601}. This enables LLMs to chain calls and extract required fields.
• Add error handling guidance. E.g., 'If Get-QiitaItem returns 404, the article ID is invalid. Try search_qiita_items() with keywords first.' This helps LLMs recover from failures.