Skip to main content
Glama
BACH-AI-Tools

Clinical Trials MCP Server

get_trial_statistics

Analyze clinical trial data by grouping aggregate statistics across phases, statuses, study types, conditions, or sponsors to identify research trends and patterns.

Instructions

Get aggregate statistics about clinical trials

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupByNoField to group statistics by
filtersNoOptional filters to apply

Implementation Reference

  • Handler implementation for the get_trial_statistics tool.
    private async handleGetTrialStatistics(args: any) {
      // For statistics, we'll make a broader search and analyze the results
      const params: any = {
        format: "json",
        pageSize: 100, // Get more results for better statistics
      };
    
      // Apply filters if provided
      if (args?.filters?.condition) {
        params["query.cond"] = args.filters.condition;
      }
      if (args?.filters?.phase) {
        params["filter.phase"] = args.filters.phase;
      }
      if (args?.filters?.status) {
        params["filter.overallStatus"] = args.filters.status;
      }
    
      try {
        const response: AxiosResponse<StudySearchResponse> =
          await this.axiosInstance.get("/studies", { params });
    
        const studies = response.data.studies || [];
        const stats = this.calculateStatistics(studies, args?.groupBy);
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  totalStudies: response.data.totalCount || 0,
                  analyzedStudies: studies.length,
                  groupBy: args?.groupBy || "none",
                  filters: args?.filters || {},
                  statistics: stats,
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [
              {
                type: "text",
                text: `Clinical Trials API error: ${
                  error.response?.data?.message || error.message
                }`,
              },
            ],
            isError: true,
          };
        }
        throw error;
      }
    }
  • src/index.ts:277-298 (registration)
    Tool definition and schema registration for get_trial_statistics.
      name: "get_trial_statistics",
      description: "Get aggregate statistics about clinical trials",
      inputSchema: {
        type: "object",
        properties: {
          groupBy: {
            type: "string",
            description: "Field to group statistics by",
            enum: ["phase", "status", "studyType", "condition", "sponsor"],
          },
          filters: {
            type: "object",
            description: "Optional filters to apply",
            properties: {
              condition: { type: "string" },
              phase: { type: "string" },
              status: { type: "string" },
            },
          },
        },
      },
    },
  • Helper functions to calculate statistics from study data.
    private calculateStatistics(studies: Study[], groupBy?: string) {
      if (!groupBy) {
        return {
          totalStudies: studies.length,
          byStatus: this.groupByField(studies, "status"),
          byPhase: this.groupByField(studies, "phase"),
          byStudyType: this.groupByField(studies, "studyType"),
        };
      }
    
      return this.groupByField(studies, groupBy);
    }
    
    private groupByField(studies: Study[], field: string) {
      const groups: { [key: string]: number } = {};
    
      studies.forEach((study) => {
        let value: string | string[];
    
        switch (field) {
          case "status":
            value = study.protocolSection.statusModule.overallStatus;
            break;
          case "phase":
            value =
              study.protocolSection.designModule?.phases?.[0] || "Not specified";
            break;
          case "studyType":
            value = study.protocolSection.designModule?.studyType || "Unknown";
            break;
          case "condition":
            value =
              study.protocolSection.conditionsModule?.conditions?.[0] ||
              "Not specified";
            break;
          case "sponsor":
            value =
              study.protocolSection.sponsorCollaboratorsModule?.leadSponsor
                ?.name || "Not specified";
            break;
          default:
            value = "Unknown";
        }
    
        const key = Array.isArray(value) ? value[0] : value;
        groups[key] = (groups[key] || 0) + 1;
      });
    
      return groups;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get aggregate statistics' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or provides any information about the format or scope of the statistics returned. For a tool with no annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately front-loaded with the essential information, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of statistical aggregation, the lack of annotations, and no output schema, the description is incomplete. It doesn't explain what kind of statistics are returned (counts, averages, distributions), how results are formatted, or any limitations of the aggregation. For a tool with 2 parameters and no structured output documentation, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for both parameters. The baseline score of 3 is appropriate since the schema adequately documents the parameters, though the description could have provided additional context about how grouping and filtering work together.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get aggregate statistics') and resource ('about clinical trials'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its many sibling tools that also retrieve clinical trial information, such as 'get_study_details' or 'get_studies_with_results', which would require a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With 15 sibling tools on the server, including various search and retrieval functions, the lack of any usage context leaves the agent guessing about appropriate scenarios for statistical aggregation versus other operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/ClinicalTrials-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server