MCP Server Scaffold
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 |
|---|---|
| echoB | Echo back the provided message |
| get_current_timeB | Get the current date and time |
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 2 tools
The two tools have completely distinct purposes: 'echo' handles message repetition while 'get_current_time' provides temporal information. There is no overlap in functionality, making it impossible to confuse them.
The naming is mixed: 'echo' uses a simple verb form while 'get_current_time' follows a verb_noun pattern. Although both are readable, they lack a consistent convention, which could lead to unpredictability if more tools were added.
With only 2 tools, this server feels thin for a 'scaffold' purpose, which typically implies a foundation for building more functionality. The count is too low to demonstrate meaningful coherence or coverage for most domains.
Given the vague 'scaffold' domain, it's hard to assess completeness, but the tools cover basic utility operations (echo and time). However, there are obvious gaps for a scaffold, such as file manipulation or configuration tools, limiting its usefulness as a foundation.