MCP Server Template
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthB | Retorna o status do servidor MCP. |
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 'health' has a clearly distinct and singular purpose of returning server status.
A single tool inherently has perfect naming consistency as there are no other tools to compare against. The name 'health' is clear and follows a simple noun pattern.
One tool is too few for a server described as a 'template', which implies a broader scope or example set. A template should ideally demonstrate multiple tools to guide users, making this count inappropriate for the stated purpose.
The server is severely incomplete for a template purpose, as it only provides a health check tool with no other functionality. This leaves significant gaps, failing to cover any meaningful domain or provide a useful example surface.