Notes 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 |
|---|---|
| addC | Add two numbers |
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 tool 'add' has a clear and distinct purpose of adding two numbers, leaving no room for confusion or misselection by an agent.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'add' follows a simple verb pattern, and with no other tools to compare against, there are no deviations or inconsistencies in naming conventions.
A single tool is too few for a server named 'Notes MCP Server', which implies functionality related to managing notes. The tool 'add' for adding numbers does not align with the expected scope, resulting in a significant mismatch between the server's purpose and the provided tools.
The server is severely incomplete for its apparent domain of notes management. With only a basic arithmetic tool, there are no operations for creating, reading, updating, or deleting notes, leading to obvious gaps that will cause agent failures in handling notes-related tasks.