Simple 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 |
|---|---|
| getNoteD | – |
| getAllNotesD | – |
| createNoteD | – |
| updateNoteD | – |
| deleteNoteD | – |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: createNote, deleteNote, getAllNotes, getNote, and updateNote cover different CRUD operations on notes. The action (create, delete, get, update) and scope (all vs. single) make them easily distinguishable.
All tools follow a consistent verbNoun pattern in camelCase (e.g., createNote, deleteNote). The naming is uniform across all five tools, with no deviations in style or convention.
With 5 tools, this server is well-scoped for managing notes, covering essential CRUD operations. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain.
The tool set provides complete CRUD coverage for notes: create, read (get and getAll), update, and delete. There are no obvious gaps, as all lifecycle operations are included, allowing agents to handle full workflows without dead ends.