usefastmcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| roll_diceA | This method will return number between 1 to 6, when asked to roll a dice. |
| add_numberA | Add 2 numbers and returns result |
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
roll_dice and add_number are completely distinct in purpose and behavior. There is no ambiguity about which tool to select for a given task.
Both tool names follow a consistent verb_noun pattern: roll_dice and add_number. The naming style is uniform and predictable.
With only two tools, the server feels quite thin. While each tool has a basic utility purpose, the set is minimal and barely provides enough surface to be considered a coherent collection.
There is no clear domain or lifecycle being covered; the tools are unrelated utilities. Obvious complementary operations (e.g., subtract, multiply, or dice with custom sides) are absent, leaving the surface feeling arbitrary and incomplete.