TypeScript MCP Sample 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 |
|---|---|
| completionD | – |
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 ambiguity or overlap between tools. The single tool 'completion' stands alone with no other tools to confuse it with.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The name 'completion' follows a clear, simple pattern with no deviations.
A single tool is too few for a server named 'TypeScript MCP Sample Server', which suggests a broader purpose like code assistance or development tasks. One tool feels thin and insufficient for such a scope, limiting functionality.
The tool set is severely incomplete for the inferred domain of TypeScript development. With only a 'completion' tool and no description, it lacks essential operations like code analysis, refactoring, or error checking, leaving significant gaps in coverage.