Skip to main content
Glama
Aki894
by Aki894

get_study_details

Retrieve comprehensive clinical trial information using the NCT ID to access study details, safety profiles, and adverse event data for drug assessment.

Instructions

Get detailed information about a specific clinical trial by NCT ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nct_idYesNCT ID of the study. Example: 'NCT04267848'

Implementation Reference

  • The actual implementation of the get_study_details tool.
    private async getStudyDetails(nctId: string) {
      const data = await this.getStudyByNCT(nctId);
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              nct_id: nctId,
              study_details: data
            }, null, 2)
          }
        ]
      };
    }
  • src/index.ts:152-164 (registration)
    Tool registration for get_study_details in MCP.
    {
      name: "get_study_details",
      description: "Get detailed information about a specific clinical trial by NCT ID",
      inputSchema: {
        type: "object",
        properties: {
          nct_id: {
            type: "string",
            description: "NCT ID of the study. Example: 'NCT04267848'"
          }
        },
        required: ["nct_id"]
      }
  • The switch case handling the execution of the get_study_details tool.
    case "get_study_details":
      if (!args.nct_id) {
        throw new McpError(ErrorCode.InvalidParams, "NCT ID is required");
      }
      return await this.getStudyDetails(args.nct_id);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get'), but doesn't mention potential errors (e.g., invalid NCT ID), rate limits, authentication needs, or what happens if the study isn't found. This leaves significant gaps for a tool that likely interacts with an external database.

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 front-loads the core purpose ('Get detailed information') without any wasted words. It directly addresses what the tool does and how to identify the resource, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and parameter context, but lacks details on return values, error handling, or behavioral traits, which are important for a read operation in a clinical context.

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 input schema has 100% description coverage, with the parameter 'nct_id' well-documented in the schema. The description adds no additional meaning beyond implying the parameter is required for lookup, so it meets the baseline of 3 without compensating for any gaps.

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 verb 'Get' and the resource 'detailed information about a specific clinical trial', specifying the identifier type 'by NCT ID'. It distinguishes from siblings like 'search_clinical_trials' by focusing on retrieval of a single study rather than searching. However, it doesn't explicitly mention what details are included, keeping it at a 4.

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

Usage Guidelines3/5

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

The description implies usage when you have a specific NCT ID, contrasting with 'search_clinical_trials' for broader queries. However, it lacks explicit guidance on when not to use it (e.g., for multiple studies) or alternatives beyond the sibling name, making it only implied rather than explicit.

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/Aki894/mcp-ClinicalTrial'

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