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
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 |
|---|---|
| add-noteC | Add a new note |
| createEventC | Create a new Google Calendar event |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-notes | Creates a summary of all notes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve completely different domains: notes and calendar events. There is no overlap or confusion possible.
Tool names use inconsistent conventions: 'add-note' uses snake_case with hyphen, while 'createEvent' uses camelCase. No consistent pattern.
With only two tools, the server feels underdeveloped for a generic Python MCP server. A more complete set would have at least 5-10 tools to justify its name.
The server covers only a single operation each for notes and events. Missing essential operations like list, delete, or update for both domains, leaving significant gaps.