NPM Package Docs MCP
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 |
|---|---|
| get_docs_for_npm_packageC | Get the docs for an 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 or overlap between tools. The tool's purpose is singular and clearly defined, making disambiguation perfect.
The single tool name follows a clear verb_noun pattern (get_docs_for_npm_package), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool for an 'NPM Package Docs' server feels too thin and under-scoped. The server's purpose suggests potential for more operations like searching packages, listing versions, or getting specific documentation sections, but only one basic retrieval tool is provided.
The tool surface is severely incomplete for the apparent domain of npm package documentation. It only allows getting docs for a package, with no support for operations like searching, filtering, or handling multiple packages, which are likely needed for effective agent workflows.