py-mcp-server-template
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pingD | – |
| get_jokeD | – |
| get_weatherD | – |
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 resource: ping is a health check, joke and weather are distinct data categories. There is no overlap or ambiguity between them.
All three tools follow the same get_<noun> snake_case pattern. The verb is uniform and the nouns are clear, so the naming convention is perfectly consistent.
At three tools, the server is at the lower end of the ideal range but still reasonable for a template or demo server. Each tool is minimal and serves as an example, though the set is slightly thin for a general-purpose utility server.
The tools do not form a coherent domain; ping, joke, and weather are unrelated, with no lifecycle or deeper operations. As a template the surface may be intentional, but for any real use it is severely incomplete, e.g., weather lacks location/forecast controls and jokes have no variations.