Skip to main content
Glama
Augmented-Nature

OpenTargets MCP Server

get_disease_details

Retrieve comprehensive disease information from OpenTargets platform using EFO ID to support gene-drug-disease association research.

Instructions

Get comprehensive disease information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDisease EFO ID

Implementation Reference

  • The handler function that implements the get_disease_details tool. It validates the input args, executes a GraphQL query to fetch disease details (id, name, description) by EFO ID, and returns the response as text content or an error.
    private async handleGetDiseaseDetails(args: any) {
      if (!isValidIdArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Disease ID is required');
      }
    
      try {
        const query = `query GetDisease($efoId: String!) { disease(efoId: $efoId) { id name description } }`;
    
        const response = await this.graphqlClient.post('', {
          query,
          variables: {
            efoId: args.id
          }
        });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error getting disease details: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition for the get_disease_details tool, specifying the required 'id' parameter as a string (Disease EFO ID).
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Disease EFO ID' },
      },
      required: ['id'],
    },
  • src/index.ts:274-284 (registration)
    Registration of the get_disease_details tool in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'get_disease_details',
      description: 'Get comprehensive disease information',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Disease EFO ID' },
        },
        required: ['id'],
      },
    },
  • src/index.ts:302-303 (registration)
    Dispatch case in the main request handler that routes 'get_disease_details' calls to the specific handler method.
    case 'get_disease_details':
      return this.handleGetDiseaseDetails(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'gets' information, implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what 'comprehensive' entails (e.g., format, depth). This leaves significant gaps for a tool with no annotation coverage.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words. It is appropriately sized for a simple tool, though it could be more front-loaded with key details like the required EFO ID.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'comprehensive disease information' includes (e.g., fields, structure), nor does it address behavioral aspects like permissions or limitations, leaving the agent with insufficient context for reliable use.

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 schema description coverage is 100%, with the single parameter 'id' documented as 'Disease EFO ID'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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') and resource ('comprehensive disease information'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'search_diseases' or 'get_disease_targets_summary' beyond the general scope of disease information.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an EFO ID), exclusions, or comparisons to siblings like 'search_diseases' for broader queries or 'get_disease_targets_summary' for target-related details.

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/Augmented-Nature/OpenTargets-MCP-Server'

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