Skip to main content
Glama
Aditya-Khadye

mcp-clinical-doc-agent

by Aditya-Khadye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ANTHROPIC_API_KEYNoOptional API key for Anthropic to use Claude Haiku 4.5 for summarization; if not set, falls back to deterministic template.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_documentsA

List all clinical trial protocol documents available in the data directory.

Returns one entry per protocol with id, title, path, indication, and phase.
Use this tool first to discover what documents are available, then pass an
``id`` from the result to ``extract_entities`` or ``summarize_protocol``.
extract_entitiesA

Extract clinical entities (drugs, conditions, interventions, endpoints, populations).

If ``document_id`` is omitted, runs across every document and returns the combined set.
Each entity carries its source ``document_id`` so callers can group results.
cluster_adverse_eventsA

Identify and group adverse-event mentions across one or more protocols.

Returns clusters bucketed by body system (gastrointestinal, cardiovascular,
neurological, dermatological, hematological, hepatic, respiratory, infections,
metabolic, other). If ``document_ids`` is omitted, clusters across all protocols.
summarize_protocolA

Generate a structured summary of a single protocol.

Returns phase, indication, intervention, primary endpoint, planned enrollment,
adverse-event count, and a 3-4 sentence narrative. Uses Claude (Haiku) when
``ANTHROPIC_API_KEY`` is set; otherwise falls back to a deterministic template.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing documents, extracting entities, clustering adverse events, and summarizing protocols. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., cluster_adverse_events, extract_entities), making them predictable and easy to distinguish.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose of clinical document analysis. Each tool fills a necessary role without redundancy or excessive granularity.

Completeness4/5

The set covers key functions: discovery, entity extraction, AE clustering, and summarization. Minor gaps exist (e.g., no search or cross-protocol comparison), but core workflows are supported.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources