MCP Duty Pharma
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_nearby_duty_pharmaciesB | Get ten closest pharmacies on duty today, sorted by distance to the given address. |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name follows a clear verb_noun pattern (get_nearby_duty_pharmacies).
One tool is too few for a server with a domain like pharmacy duty information, as it lacks essential operations such as filtering by time, getting pharmacy details, or updating duty status. This severely limits agent functionality.
The tool surface is severely incomplete for the domain; it only provides a list of nearby duty pharmacies without supporting operations like checking specific pharmacy hours, verifying duty status, or managing pharmacy data, leading to significant gaps in agent workflows.