Qmed-AskCPG
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASKCPG_API_KEY | Yes | API key for AskCPG service. Contact maintainer to obtain. | |
| ASKCPG_BACKEND | Yes | Backend URL for AskCPG service. Contact maintainer to obtain. |
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_cpg_contextC | Get context from medical clinical practice guideline books based on user 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 risk of confusion between tools. The agent can uniquely identify the tool's purpose.
The single tool name 'get_cpg_context' follows a clear verb_noun pattern, consistent with common MCP naming conventions.
A single tool for querying clinical guidelines is minimalist but functional. The server's scope is narrow, yet a few more tools (e.g., list_guidelines) could improve coverage.
The server provides only retrieval of context from medical books. Missing operations like listing available guidelines or retrieving full sections, but the tool may suffice for simple Q&A tasks.