mcp-npm-package-documentation
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| npm-package-documentationD | Documentation for the npm package. |
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 between tools. The tool's purpose is clearly tied to the server's domain.
The single tool name 'npm-package-documentation' is descriptive and consistent. No competing patterns exist, so naming is effectively coherent.
The tool count is at the thin edge—one tool can fulfill a very specific purpose, but it feels minimal for a server. It is borderline but acceptable.
For a documentation-only server, the single tool may cover the main use case, but the vague description leaves potential gaps (e.g., versioning, search) unaddressed.