Python MCP 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetD | – |
| addNumbersD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| codeReview | Generate a code review prompt for the given language and code |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| getServerStatus | Get current server satus information |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: addNumbers performs a mathematical operation, while greet handles a social interaction. There is no overlap or ambiguity between them, making misselection unlikely.
The naming is inconsistent: addNumbers uses camelCase, while greet uses lowercase. There is no predictable pattern across the set, though both names are readable individually.
With only 2 tools, the server feels thin and under-scoped for a general-purpose Python MCP server. This minimal set suggests limited functionality that may not cover typical Python-related tasks.
The tool surface is severely incomplete for a Python server domain. It lacks basic operations like code execution, file handling, or library management, leaving obvious gaps that will cause agent failures in practical scenarios.