Skip to main content
Glama
Augmented-Nature

ChEMBL MCP Server

search_drug_indications

Find drugs and their therapeutic uses by searching disease indications and filtering by drug type to identify treatment options.

Instructions

Search for therapeutic indications and disease areas

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indicationYesDisease or indication search term
drug_typeNoDrug type filter (e.g., Small molecule, Antibody)
limitNoNumber of results to return (1-1000, default: 25)

Implementation Reference

  • The handler function that implements the core logic for the 'search_drug_indications' tool. It validates input, queries the ChEMBL API /drug_indication.json endpoint with the indication search term, and returns the JSON results.
    private async handleSearchDrugIndications(args: any) {
      if (!args || typeof args.indication !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid drug indications arguments');
      }
    
      try {
        const response = await this.apiClient.get('/drug_indication.json', {
          params: {
            q: args.indication,
            limit: args.limit || 25,
          },
        });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to search drug indications: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • The input schema definition for the 'search_drug_indications' tool, specifying parameters like indication (required), drug_type, and limit.
    name: 'search_drug_indications',
    description: 'Search for therapeutic indications and disease areas',
    inputSchema: {
      type: 'object',
      properties: {
        indication: { type: 'string', description: 'Disease or indication search term' },
        drug_type: { type: 'string', description: 'Drug type filter (e.g., Small molecule, Antibody)' },
        limit: { type: 'number', description: 'Number of results to return (1-1000, default: 25)', minimum: 1, maximum: 1000 },
      },
      required: ['indication'],
    },
  • src/index.ts:782-783 (registration)
    Registration of the tool handler in the main CallToolRequestSchema switch statement, mapping the tool name to its handler function.
    case 'search_drug_indications':
      return await this.handleSearchDrugIndications(args);
  • src/index.ts:612-624 (registration)
    Tool registration in the ListToolsRequestSchema response, defining the tool's name, description, and input schema.
    {
      name: 'search_drug_indications',
      description: 'Search for therapeutic indications and disease areas',
      inputSchema: {
        type: 'object',
        properties: {
          indication: { type: 'string', description: 'Disease or indication search term' },
          drug_type: { type: 'string', description: 'Drug type filter (e.g., Small molecule, Antibody)' },
          limit: { type: 'number', description: 'Number of results to return (1-1000, default: 25)', minimum: 1, maximum: 1000 },
        },
        required: ['indication'],
      },
    },
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. While 'search' implies a read-only operation, the description doesn't address important behavioral aspects like authentication requirements, rate limits, pagination behavior, or what format the results will be returned in. It provides minimal context beyond the basic operation.

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 extremely concise at just 7 words, front-loading the core functionality without any unnecessary elaboration. Every word earns its place by communicating the essential purpose, though this brevity comes at the cost of completeness.

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?

For a search tool with 3 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what kind of results to expect, how results are structured, whether there's pagination, or how the search functionality differs from the many other search tools in the sibling list.

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?

With 100% schema description coverage, the input schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples of effective search terms, or clarify how the parameters interact during search execution.

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 tool's purpose as searching for therapeutic indications and disease areas, which is a specific verb+resource combination. However, it doesn't differentiate itself from sibling tools like 'search_drugs', 'search_compounds', or 'search_targets' which might overlap in pharmaceutical search functionality.

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 many sibling search tools available (search_drugs, search_compounds, search_targets, etc.), there's no indication of what makes this tool distinct or when it should be preferred over other search options.

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/ChEMBL-MCP-Server'

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