TypeScript 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 |
|---|---|
| calculatorB | A safe calculator that can evaluate mathematical expressions. |
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 has a clear and distinct purpose, making it impossible for an agent to misselect between tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'calculator' follows a clear noun-based pattern, which is appropriate for its function, and there are no other tools to compare it against for inconsistency.
A single tool is generally too few for a server's purpose, as it limits functionality and scope. While the tool is well-defined, the server likely lacks coverage for broader TypeScript-related tasks, making the count inappropriate for the implied domain.
The server is severely incomplete for a TypeScript domain, as it only offers a calculator tool with no other TypeScript-specific operations like code analysis, compilation, or linting. This represents a significant gap that will cause agent failures in handling TypeScript tasks.