Example MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| PYTHONPATH | No | Python path for module resolution |
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 |
|---|---|
| calculateA | Evaluate a mathematical expression safely. Args: expression: A mathematical expression to evaluate (e.g., "2 + 2", "10 * 5") Returns: The result of the calculation as a string |
| greetB | Generate a friendly greeting message. Args: name: The name of the person to greet Returns: A personalized greeting message |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| help | Provide help information about available tools and resources. Returns: Help text describing the server's capabilities |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_settings | Get server configuration settings. Returns: A dictionary containing server settings |
| get_server_info | Get general server information. Returns: A dictionary containing server information |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: 'calculate' handles mathematical expressions, while 'greet' generates personalized greetings. There is no overlap in functionality, making it impossible to confuse them.
Both tool names follow a simple verb-only pattern ('calculate', 'greet'), which is consistent and predictable. There are no mixed conventions or deviations in naming style.
With only 2 tools, the server feels thin and under-scoped for a general-purpose 'Example MCP Server'. This minimal set lacks the depth needed to handle a coherent domain or typical workflows effectively.
The server's purpose is unclear from the tools provided, but the surface is severely incomplete for any meaningful domain. There are obvious gaps, such as missing related operations (e.g., no other utilities or extended functionality), which will limit agent capabilities.