Skip to main content
Glama
Augmented-Nature

ChEMBL MCP Server

search_targets

Find biological targets by name, type, or organism to support drug discovery and research.

Instructions

Search for biological targets by name or type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesTarget name or search query
target_typeNoTarget type filter (e.g., SINGLE PROTEIN, PROTEIN COMPLEX)
organismNoOrganism filter
limitNoNumber of results to return (1-1000, default: 25)

Implementation Reference

  • The handler function that implements the core logic of the 'search_targets' tool by querying the ChEMBL '/target/search.json' API endpoint with the search query and limit parameters.
    private async handleSearchTargets(args: any) {
      try {
        const response = await this.apiClient.get('/target/search.json', {
          params: { q: args.query, 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 targets: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • The JSON schema defining the input parameters for the 'search_targets' tool, including required 'query' and optional filters.
    inputSchema: {
      type: 'object',
      properties: {
        query: { type: 'string', description: 'Target name or search query' },
        target_type: { type: 'string', description: 'Target type filter (e.g., SINGLE PROTEIN, PROTEIN COMPLEX)' },
        organism: { type: 'string', description: 'Organism filter' },
        limit: { type: 'number', description: 'Number of results to return (1-1000, default: 25)', minimum: 1, maximum: 1000 },
      },
      required: ['query'],
    },
  • src/index.ts:459-471 (registration)
    The tool registration in the ListTools response, defining name, description, and input schema for 'search_targets'.
      name: 'search_targets',
      description: 'Search for biological targets by name or type',
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'Target name or search query' },
          target_type: { type: 'string', description: 'Target type filter (e.g., SINGLE PROTEIN, PROTEIN COMPLEX)' },
          organism: { type: 'string', description: 'Organism filter' },
          limit: { type: 'number', description: 'Number of results to return (1-1000, default: 25)', minimum: 1, maximum: 1000 },
        },
        required: ['query'],
      },
    },
  • src/index.ts:759-760 (registration)
    The dispatch case in the CallToolRequestSchema handler that routes calls to the 'search_targets' handler function.
      return await this.handleGetTargetInfo(args);
    case 'get_target_compounds':
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, what the output format might be (e.g., list of targets with fields), any rate limits, authentication needs, or how results are sorted. 'Search' implies querying, but specifics are missing.

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 with no wasted words. It's front-loaded with the core purpose, making it easy for an agent to parse quickly. Every part of the sentence contributes to understanding the tool's function.

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 a search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'biological targets' entail, how results are returned, or any limitations (e.g., pagination, default behaviors). For a tool in a scientific context with many siblings, 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?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds minimal value beyond the schema—it mentions 'name or type' which aligns with 'query' and 'target_type' parameters but doesn't provide additional context like example queries or how filters combine.

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 ('Search for') and resource ('biological targets'), with specific search criteria ('by name or type'). It distinguishes from most siblings like 'search_compounds' or 'search_drugs' by focusing on targets, though it doesn't explicitly differentiate from 'get_target_info' which might retrieve rather than search.

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 on when to use this tool versus alternatives is provided. It doesn't mention siblings like 'advanced_search' (which might offer more filters) or 'search_by_uniprot' (for specific identifier searches), leaving the agent to infer usage context from tool names alone.

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