FastMCP Demo 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
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| roll_diceA | Roll n_dice 6-sided dice and return the results. |
| add_numbersB | Add two numbers together. |
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_numbers target completely different operations with no overlap; an agent can easily tell them apart.
Both names follow a consistent snake_case verb_noun pattern (roll_dice, add_numbers), making the convention predictable.
Two tools is borderline thin even for a demo server; while each is distinct, the set lacks enough surface to demonstrate a coherent toolkit.
There is no clear domain, so completeness is hard to assess; each tool is self-contained but the surface is minimal and offers no lifecycle or related operations.