SouthAsia MCP Tool
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 |
|---|---|
| mcp_hello_worldB | A simple demonstration tool that returns a greeting message |
| mcp_hello_nameB | A demonstration tool that greets you by name |
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 distinct purposes: one greets by name and the other returns a generic greeting. While both involve greetings, the specific functionality differs enough to avoid confusion, though the overlap in greeting theme could cause minor ambiguity if not carefully read.
Both tools follow a consistent naming pattern with 'mcp_' prefix and descriptive suffixes ('hello_name' and 'hello_world'). This uniformity makes it easy to predict and understand the tool set's structure.
With only 2 tools, the server feels under-scoped for a general-purpose MCP server, as it lacks coverage for typical operations beyond basic greetings. This minimal count suggests limited utility for complex agent tasks.
Inferred as a demonstration or greeting server, the tool set is severely incomplete—it only offers greeting functions without any CRUD, data manipulation, or broader utility operations. This leaves obvious gaps for practical agent workflows.