Basic 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 |
|---|---|
| hello_worldC | Devuelve un saludo básico. |
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. The tool 'hello_world' has a single, clear purpose that cannot be mistaken for any other functionality.
The single tool name 'hello_world' follows a common snake_case pattern, and since there is only one tool, consistency is inherently perfect. There are no other tools to compare against, so no inconsistencies can arise.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. While it might be appropriate for a minimal demo, it feels thin and inadequate for any real-world application or domain coverage.
The server's purpose is unclear from the single tool, but for any inferred domain (e.g., greetings or basic interactions), the surface is severely incomplete. With only a 'hello_world' tool, there are obvious gaps in operations like customization, querying, or other related actions, making it impossible to perform meaningful workflows.