Meu MCP
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 |
|---|---|
| saudacaoA | Cria uma mensagem de saudação para uma pessoa. |
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
There is only one tool, so there is no possibility of overlap or ambiguity. The tool has a clear, single purpose.
With only one tool named 'saudacao', there is no naming pattern to violate. The name is clear and accurately reflects its function.
A single trivial tool is far too few for a typical MCP server, which usually exposes a broader set of related operations. Even for a greeting service, one operation feels insufficient.
The single tool covers the basic greeting use case, but there are no complementary operations (e.g., formatting variations, language selection) or obvious extensions, leaving the surface noticeably thin.