DoctorVerify
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 |
|---|---|
| registration_lookup_guideA | Get the correct, official manual steps to verify an Indian doctor's registration. |
| search_doctor_registrationA | Search the live Indian Medical Register and return real matches. |
| get_doctor_profileA | Get the full IMR profile for one specific match from search_doctor_registration. |
| check_blacklistA | Check the live NMC list of suspended/struck-off doctors. |
| flag_lookalike_domainB | Check whether a link is the official NMC domain or a known lookalike. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| verify_doctor_checklist | Walk through everything worth checking before trusting a doctor's credentials. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| official_sources | Where Indian medical credentials actually get verified, and by whom. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: live register search, blacklist check, profile detail, manual fallback guide, and domain safety check. There is no real overlap, and the descriptions reinforce the boundaries between search, blacklist, and guide.
Most tool names follow a clear verb_noun pattern in snake_case: check_blacklist, flag_lookalike_domain, search_doctor_registration, get_doctor_profile. The one outlier is registration_lookup_guide, which is a noun phrase rather than a verb-led name, making the convention mostly but not fully consistent.
Five tools is a well-scoped set for a doctor verification server. Each tool addresses a distinct part of the verification workflow without redundancy or bloat.
The tool set covers the core verification lifecycle: live register search, blacklist screening, detailed profile retrieval, a manual fallback guide, and domain legitimacy checking. No obvious dead ends or missing operations for the stated purpose of verifying an Indian doctor's registration.