Python Docs 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 |
|---|---|
| get_python_docsC | Get Python documentation for a given query |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as retrieving Python documentation, making it distinct by default.
The single tool name 'get_python_docs' follows a clear verb_noun pattern (get + python_docs). Since there is only one tool, consistency is inherently perfect with no deviations to assess.
A single tool is too few for a server named 'Python Docs Server', which suggests a broader scope like searching, browsing, or managing documentation. One tool feels thin and limits functionality, indicating a mismatch with the apparent purpose.
The tool set is severely incomplete for a documentation server. It only provides retrieval ('get_python_docs'), lacking essential operations such as search, list topics, get specific versions, or navigate documentation structure, which are typical for such a domain.