MCP Add 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 |
|---|---|
| addD | – |
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 confusion or overlap with other tools. The single tool 'add' stands alone without any ambiguity in purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'add' is straightforward and follows a simple verb pattern.
A single tool is generally too few for most server purposes, as it limits functionality and scope. Without a description, it's unclear if this minimal set is justified, but typically one tool feels thin and incomplete.
With only one tool and no description, it is impossible to assess coverage of any domain. The surface is severely incomplete, lacking any context or additional operations that might be expected for a coherent toolset.