Node.js 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 |
|---|---|
| calculateD | – |
| get_system_infoD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| system |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'calculate' likely performs mathematical or computational operations, while 'get_system_info' retrieves system-related data. There is no overlap or ambiguity between these functions, making them easy for an agent to differentiate.
The naming is inconsistent: 'calculate' uses a bare verb with no noun, while 'get_system_info' follows a verb_noun pattern. This mixing of conventions lacks a predictable pattern, though the names are still readable.
With only 2 tools, this server feels too thin for a general-purpose Node.js domain, which typically involves many operations like file handling, networking, or process management. The count is insufficient to cover the implied scope effectively.
The tool surface is severely incomplete for a Node.js server, lacking basic operations such as file I/O, module management, or process control. The two tools provided do not offer meaningful coverage, leaving significant gaps that will cause agent failures.