FastMCP Demo
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 |
|---|---|
| helloC | A simple greeting tool that says hello |
| calculateC | Perform basic arithmetic calculations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| greet_user | Generate a greeting message |
| explain_mcp | Get an explanation of what MCP is |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Example Resource | A simple example resource |
| Server Configuration | Current server configuration |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: 'calculate' handles arithmetic operations, while 'hello' provides a greeting. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tool names follow a consistent pattern of using simple, descriptive verbs ('calculate', 'hello') without any mixing of conventions like camelCase or snake_case. The naming is straightforward and predictable.
With only two tools, the server feels thin and under-scoped for a general-purpose demo. While the tools are distinct, the count is too low to meaningfully cover a domain or provide a coherent set of operations, limiting utility.
The server lacks a clear domain, making it impossible to assess coverage meaningfully. The tools are trivial and unrelated (arithmetic and greeting), offering no cohesive workflow or lifecycle, which severely limits agent functionality.