Public 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 |
|---|---|
| addA | 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 confusion or overlap between tools, as there are no other tools to compare it against. The tool's purpose is singular and clear.
Since there is only one tool, naming consistency is inherently perfect; there are no other names to be inconsistent with. The tool name 'add' is simple and follows a verb-only pattern, which is acceptable for a single tool.
A single tool is generally too few for most server purposes, as it limits functionality and suggests an incomplete or trivial scope. For a server named 'Public MCP Server', which implies broader utility, one tool is insufficient and mismatched.
The server's domain is unclear from the name and single tool, but a tool that only adds two numbers is severely incomplete for any plausible public utility purpose. There are obvious gaps, such as missing other arithmetic operations or broader functionalities.