Skip to main content
Glama
Augmented-Nature

ChEMBL MCP Server

analyze_admet_properties

Analyze ADMET properties (Absorption, Distribution, Metabolism, Excretion, Toxicity) for compounds using ChEMBL IDs to assess drug safety and pharmacokinetics.

Instructions

Analyze ADMET properties (Absorption, Distribution, Metabolism, Excretion, Toxicity)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chembl_idYesChEMBL compound ID

Implementation Reference

  • Main handler function that executes the analyze_admet_properties tool. Fetches ChEMBL compound data and computes ADMET analysis including absorption, distribution, and drug-likeness assessments.
    private async handleAnalyzeAdmetProperties(args: any) {
      if (!isValidChemblIdArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid ADMET analysis arguments');
      }
    
      try {
        const response = await this.apiClient.get(`/molecule/${args.chembl_id}.json`);
        const molecule = response.data;
        const props = molecule.molecule_properties || {};
    
        // Analyze ADMET-related properties from ChEMBL data
        const admetAnalysis = {
          chembl_id: args.chembl_id,
          absorption: {
            molecular_weight: props.full_mwt || props.molecular_weight,
            alogp: props.alogp,
            hbd: props.hbd,
            hba: props.hba,
            psa: props.psa,
            ro3_pass: props.ro3_pass,
            assessment: this.assessAbsorption(props),
          },
          distribution: {
            logp: props.alogp,
            psa: props.psa,
            assessment: this.assessDistribution(props),
          },
          drug_likeness: {
            lipinski_violations: props.num_ro5_violations,
            rotatable_bonds: props.rtb,
            aromatic_rings: props.aromatic_rings,
            assessment: this.assessDrugLikeness(props),
          },
          molecular_properties: props,
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(admetAnalysis, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to analyze ADMET properties: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • src/index.ts:637-647 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the tool name, description, and input schema.
    {
      name: 'analyze_admet_properties',
      description: 'Analyze ADMET properties (Absorption, Distribution, Metabolism, Excretion, Toxicity)',
      inputSchema: {
        type: 'object',
        properties: {
          chembl_id: { type: 'string', description: 'ChEMBL compound ID' },
        },
        required: ['chembl_id'],
      },
    },
  • src/index.ts:787-788 (registration)
    Handler dispatch in the CallToolRequestSchema switch statement.
    case 'analyze_admet_properties':
      return await this.handleAnalyzeAdmetProperties(args);
  • Input schema definition for the tool, specifying required chembl_id parameter.
    inputSchema: {
      type: 'object',
      properties: {
        chembl_id: { type: 'string', description: 'ChEMBL compound ID' },
      },
      required: ['chembl_id'],
    },
  • Helper function used by the handler to assess absorption properties based on molecular descriptors.
    private assessAbsorption(props: any): string {
      const mw = props.full_mwt || props.molecular_weight || 0;
      const hbd = props.hbd || 0;
      const hba = props.hba || 0;
      const psa = props.psa || 0;
    
      if (mw > 500 || hbd > 5 || hba > 10 || psa > 140) {
        return 'Poor oral absorption predicted';
      } else if (mw < 400 && hbd <= 3 && hba <= 7 && psa < 100) {
        return 'Good oral absorption predicted';
      }
      return 'Moderate oral absorption predicted';
    }
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 analyzes ADMET properties but doesn't reveal how (e.g., via prediction models, database lookups, or calculations), what the output includes (e.g., scores, classifications, or warnings), or any constraints (e.g., rate limits, data freshness, or accuracy). For a tool with no annotations, 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 that front-loads the core purpose without unnecessary words. It uses parentheses to clarify the ADMET acronym, making it clear and well-structured. Every part of the sentence earns its place, avoiding redundancy.

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 ADMET analysis, no annotations, and no output schema, the description is incomplete. It doesn't explain what the analysis entails, the format or meaning of results, or any behavioral traits (e.g., whether it's a read-only lookup or a computational prediction). For a tool with no structured support, more context is needed to guide effective 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 input schema has 100% description coverage, with the single parameter 'chembl_id' documented as 'ChEMBL compound ID'. The description adds no additional parameter semantics beyond this, such as format examples or validation rules. With high schema coverage, the baseline is 3, as 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 tool's purpose: analyzing ADMET properties (Absorption, Distribution, Metabolism, Excretion, Toxicity) for compounds. It specifies the action ('Analyze') and the resource ('ADMET properties'), making it distinct from siblings like 'predict_solubility' or 'assess_drug_likeness'. However, it doesn't explicitly differentiate from all siblings (e.g., 'calculate_descriptors' might overlap), so it's not a perfect 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. It doesn't mention prerequisites (e.g., needing a ChEMBL ID), compare it to siblings like 'assess_drug_likeness' or 'predict_solubility', or specify use cases (e.g., for drug development vs. research). This leaves the agent with minimal context for selection.

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