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 |
|---|---|
| echoB | Echo back the input text |
| uppercaseB | Convert text to uppercase |
| calculateC | Perform basic mathematical calculations |
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 3 tools
Each tool has a clearly distinct purpose: calculate performs mathematical operations, echo returns input text unchanged, and uppercase transforms text to uppercase. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent pattern of using simple, descriptive verbs (calculate, echo, uppercase) without any mixing of conventions like camelCase or snake_case. This uniformity enhances readability and predictability.
With only 3 tools, the server feels thin for a general-purpose MCP server, as it lacks coverage for common operations like data manipulation beyond text or more advanced utilities. However, the count is not extreme and could be appropriate for a minimal utility set.
The tool set is severely incomplete for a general-purpose server, missing essential operations such as text transformation beyond uppercase (e.g., lowercase, substring), mathematical functions beyond basic calculations, or other utility tasks. This will likely cause agent failures in broader scenarios.