Sample 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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherC | Get the current weather for a specified location. |
| calculateC | Calculate the result of a mathematical expression. |
| convert_currencyC | Convert amount from one currency to another. |
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 targets a completely different task (mathematical calculation, currency conversion, and weather retrieval), so there is no ambiguity in purpose.
All tool names follow a consistent verb_noun pattern (calculate, convert_currency, get_weather), making them predictable and easy to understand.
Three tools is a reasonable number for a utility server, though the set feels slightly sparse for a general-purpose toolkit.
The tools form a disjoint set with no clear domain; they cover only a few random utilities, leaving obvious gaps for a general-purpose server.