Python MCP Server Blueprint
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 |
|---|---|
| calculate_squareA | 与えられた数値の2乗を計算する。 |
| greet_userA | ユーザーに挨拶を返す。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explain_code | 指定されたプログラミング言語のコードを解説するためのプロンプト。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_system_info | サーバーを実行しているマシンのシステム情報を取得する。 |
TDQS
Scored across 2 tools
Each tool has a clearly distinct purpose: one performs a numeric calculation, the other provides a greeting. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern (calculate_square, greet_user), making the naming consistent and predictable.
With only two tools, the server feels thin for most purposes, though as a 'blueprint' it may be intentionally minimal. The count is borderline acceptable.
The two tools are unrelated and do not form a cohesive domain, leaving significant gaps for any real-world use case. There is no apparent lifecycle or broader coverage.