DocuMind MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evaluate_readmeC | リポジトリ内の全てのREADMEファイルの構成を評価し、改善点を提案します |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clear purpose of evaluating README files in repositories.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'evaluate_readme' follows a clear verb_noun pattern.
One tool is too few for a server named 'DocuMind MCP Server', which suggests a broader documentation-related purpose. This feels thin and limited in scope, lacking coverage for other documentation tasks.
The server is severely incomplete for its implied domain of documentation management. It only handles README evaluation, missing obvious gaps like creating, updating, or analyzing other documentation types, or managing documentation workflows.