NTDeliver MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP server when MCP_TRANSPORT=http. Default is 3000. | 3000 |
| MCP_TRANSPORT | No | Transport mode: 'stdio' for local, 'http' for HTTP/SSE. Default is 'stdio'. | stdio |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ntd_schemaA | Returns column names, row count, milestone column list, known filter values, and a sample row. Call this first. |
| ntd_list_posA | List POs with optional filters. Returns key fields and milestone progress per PO. Donors: GSK, Eisai, Merck USA, Merck KGaA, J&J. Drugs: ALB, DEC, IVM, MEB, PZQ, TCZ. Regions: AFRO, AMRO, EMRO, EURO, SEARO, WPRO. |
| ntd_get_poA | Get full details and all milestone dates for a single PO by PO number. |
| ntd_get_milestonesC | Return milestone dates and progress for matching POs. Filter by PO number, country, donor, or drug. |
| ntd_milestone_completionC | Aggregate milestone completion rates (% of POs with each milestone recorded). Filter by donor, country, drug, region, year. |
| ntd_summary_statsB | PO counts and total tablet quantities grouped by a field. group_by: donor | country | drug | region | year | mode. |
| ntd_list_valuesB | All distinct values for any column. Useful for discovering valid filter values. |
| ntd_days_to_mdaB | Find POs sorted by days until planned MDA. Optionally filter and/or limit by a maximum day threshold. |
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 8 tools
Each tool has a clearly distinct purpose: schema discovery, listing/filtering POs, getting full details, milestone queries, aggregate statistics, value enumeration, and days-to-MDA analysis. No two tools overlap in function, making selection unambiguous.
All tools share the 'ntd_' prefix, but the naming convention is inconsistent: some use verb_noun ('list_pos', 'get_po', 'get_milestones', 'list_values'), while others are noun phrases ('schema', 'milestone_completion', 'summary_stats', 'days_to_mda'). This mixed pattern reduces predictability.
With eight tools, the server is well-scoped for a read-only data exploration API focused on NTD delivery POs. Each tool adds unique value without redundancy, and the count is appropriate for the domain's complexity.
The tool set covers all likely needs for querying an NTD delivery database: schema introspection, filtered lists, single-record details, milestone tracking, aggregate statistics, value discovery, and a specialized analytical query. There are no obvious gaps for a read-only server.