Skip to main content
Glama
Augmented-Nature

ChEMBL MCP Server

search_by_uniprot

Find ChEMBL targets using UniProt accession numbers to identify relevant biological targets in drug discovery research.

Instructions

Find ChEMBL targets by UniProt accession

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uniprot_idYesUniProt accession number
limitNoNumber of results to return (1-1000, default: 25)

Implementation Reference

  • The handler function for the 'search_by_uniprot' tool. It validates the uniprot_id argument, queries the ChEMBL target/search API with the UniProt ID, and returns the JSON response.
    private async handleSearchByUniprot(args: any) {
      if (!args || typeof args.uniprot_id !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid UniProt arguments');
      }
    
      try {
        const response = await this.apiClient.get('/target/search.json', {
          params: {
            q: args.uniprot_id,
            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 by UniProt: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
  • Input schema definition for the 'search_by_uniprot' tool, specifying uniprot_id as required string and optional limit.
    inputSchema: {
      type: 'object',
      properties: {
        uniprot_id: { type: 'string', description: 'UniProt accession number' },
        limit: { type: 'number', description: 'Number of results to return (1-1000, default: 25)', minimum: 1, maximum: 1000 },
      },
      required: ['uniprot_id'],
    },
  • src/index.ts:496-507 (registration)
    Registration of the 'search_by_uniprot' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'search_by_uniprot',
      description: 'Find ChEMBL targets by UniProt accession',
      inputSchema: {
        type: 'object',
        properties: {
          uniprot_id: { type: 'string', description: 'UniProt accession number' },
          limit: { type: 'number', description: 'Number of results to return (1-1000, default: 25)', minimum: 1, maximum: 1000 },
        },
        required: ['uniprot_id'],
      },
    },
  • src/index.ts:762-763 (registration)
    Dispatch/registration in the CallToolRequestSchema switch statement that routes to the handler.
    case 'search_by_uniprot':
      return await this.handleSearchByUniprot(args);
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 the action 'Find' but doesn't describe what 'Find' entails—whether it's a read-only query, what the output format might be, if there are rate limits, or authentication needs. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 zero waste—'Find ChEMBL targets by UniProt accession'. It's front-loaded with the core purpose and appropriately sized for a simple search tool.

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 tool's complexity (a search function with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'ChEMBL targets' are, what data is returned, or behavioral aspects like error handling. For a tool in a scientific context with siblings like 'advanced_search', 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%, with clear descriptions for both parameters ('uniprot_id' and 'limit'). The description adds no additional parameter semantics beyond what the schema provides, such as examples of UniProt IDs or context for the limit. Baseline 3 is appropriate when 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 verb 'Find' and the resource 'ChEMBL targets', specifying the lookup method 'by UniProt accession'. It distinguishes from siblings like 'search_targets' or 'get_target_info' by focusing on UniProt-based searching. However, it doesn't explicitly contrast with 'search_by_inchi' or other search tools, keeping it at 4 rather than 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 like 'search_targets', 'get_target_info', or 'advanced_search'. It doesn't mention prerequisites, exclusions, or specific scenarios where this tool is preferred, leaving the agent to infer usage from the name 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