TypeScript MCP Server Boilerplate
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 |
|---|---|
| greetingC | Say hello or goodbye to someone |
| calculatorB | Perform basic mathematical calculations |
| timeB | Get current date and time |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code-review | Code review prompt template |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Information | Server information and status |
| Server Statistics | Server runtime statistics |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: calculator for math, greeting for salutations, and time for date/time retrieval. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
All tool names follow a consistent pattern of simple, descriptive nouns (calculator, greeting, time). While not using a verb_noun structure, the naming is uniform and predictable across the set, enhancing readability and coherence.
With only 3 tools, the set feels thin for a server labeled as a 'TypeScript MCP Server Boilerplate,' which implies a broader utility or foundational purpose. This minimal count suggests under-scoping, as typical boilerplates might include more varied or domain-specific tools.
The tools cover unrelated, basic functions (math, greetings, time) without a clear domain, making it impossible to assess coverage meaningfully. There are significant gaps for any coherent purpose, as these tools do not form a complete surface for development, automation, or other typical boilerplate use cases.