Skip to main content
Glama
Augmented-Nature

ChEMBL MCP Server

get_target_pathways

Retrieve biological pathways linked to a specific ChEMBL target ID to understand its role in cellular processes.

Instructions

Get biological pathways associated with a target

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_chembl_idYesChEMBL target ID

Implementation Reference

  • The handler function for the 'get_target_pathways' tool. It validates the input target_chembl_id, fetches target data from ChEMBL API, extracts pathway information from cross-references (filtering Reactome, KEGG, WikiPathways), and returns formatted JSON.
    private async handleGetTargetPathways(args: any) {
      if (!args || typeof args.target_chembl_id !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid target pathways arguments');
      }
    
      try {
        // Get target information which includes pathway data
        const targetResponse = await this.apiClient.get(`/target/${args.target_chembl_id}.json`);
        const target = targetResponse.data;
    
        // Extract pathway information from target data
        const pathways = {
          target_chembl_id: args.target_chembl_id,
          target_name: target.pref_name,
          target_type: target.target_type,
          cross_references: target.cross_references || [],
          pathways: (target.cross_references || []).filter((ref: any) =>
            ref.xref_src === 'Reactome' || ref.xref_src === 'KEGG' || ref.xref_src === 'WikiPathways'
          ),
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(pathways, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get target pathways: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • The tool schema definition in the list of tools returned by ListToolsRequestSchema, including name, description, and input schema requiring 'target_chembl_id'.
      name: 'get_target_pathways',
      description: 'Get biological pathways associated with a target',
      inputSchema: {
        type: 'object',
        properties: {
          target_chembl_id: { type: 'string', description: 'ChEMBL target ID' },
        },
        required: ['target_chembl_id'],
      },
    },
  • src/index.ts:764-765 (registration)
    The registration/dispatch case in the CallToolRequestSchema handler's switch statement that routes calls to the handleGetTargetPathways function.
    case 'get_target_pathways':
      return await this.handleGetTargetPathways(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves pathways but doesn't describe what 'associated' means (e.g., direct vs. indirect), potential limitations (e.g., data availability), or output format (e.g., list of pathways with details). This is inadequate 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 the tool returns (e.g., pathway names, IDs, or full details), potential errors, or behavioral traits like rate limits. For a tool with no structured output information, 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?

The input schema has 100% description coverage, with the parameter 'target_chembl_id' clearly documented as a 'ChEMBL target ID'. The description doesn't add any additional meaning beyond this, such as format examples or validation rules, but the schema provides sufficient baseline information.

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 with a specific verb ('Get') and resource ('biological pathways associated with a target'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_target_info' or 'get_target_compounds', which might also provide target-related 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid ChEMBL ID), exclusions, or compare it to sibling tools like 'search_targets' or 'get_target_info', leaving the agent to infer usage context.

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