S/MCP - Stern Model Context Protocol
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 |
|---|---|
| hello_toolD | Hello tool |
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 'hello_tool' has a distinct purpose by default, as there are no other tools to confuse it with.
The naming follows a consistent snake_case pattern with 'hello_tool'. Since there is only one tool, the naming is inherently consistent with no deviations or mixed conventions to evaluate.
A single tool is generally too few for most server purposes, as it limits functionality and scope. For a server named 'S/MCP - Stern Model Context Protocol', one tool feels thin and insufficient to cover any meaningful domain or workflow.
The server has a single trivial tool ('hello_tool'), which suggests it is severely incomplete for any practical purpose. There are obvious gaps, as no domain or operations are covered beyond a basic greeting, making it impossible to assess coverage meaningfully.