Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

get_pharmacophore_features

Extract pharmacophore features and binding site data for PubChem compounds to support drug discovery and molecular interaction analysis.

Instructions

Get pharmacophore features and binding site information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)

Implementation Reference

  • The handler function that executes the core logic of the 'get_pharmacophore_features' tool. It currently returns a placeholder response indicating the feature is not yet implemented.
    private async handleGetPharmacophoreFeatures(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Pharmacophore features not yet implemented', args }, null, 2) }] };
    }
  • The input schema definition for the tool, specifying the required 'cid' parameter as number or string.
      name: 'get_pharmacophore_features',
      description: 'Get pharmacophore features and binding site information',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
        },
        required: ['cid'],
      },
    },
  • src/index.ts:776-777 (registration)
    Registration in the switch statement of the request handler, dispatching calls to the specific handler method.
    case 'get_pharmacophore_features':
      return await this.handleGetPharmacophoreFeatures(args);
  • src/index.ts:562-732 (registration)
    The tool is registered as part of the comprehensive tools list provided to the MCP server.
        {
          name: 'get_pharmacophore_features',
          description: 'Get pharmacophore features and binding site information',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
            },
            required: ['cid'],
          },
        },
    
        // Bioassay & Activity Data (5 tools)
        {
          name: 'search_bioassays',
          description: 'Search for biological assays by target, description, or source',
          inputSchema: {
            type: 'object',
            properties: {
              query: { type: 'string', description: 'General search query' },
              target: { type: 'string', description: 'Target protein or gene name' },
              source: { type: 'string', description: 'Data source (e.g., ChEMBL, NCGC)' },
              max_records: { type: 'number', description: 'Maximum number of results (1-1000, default: 100)', minimum: 1, maximum: 1000 },
            },
            required: [],
          },
        },
        {
          name: 'get_assay_info',
          description: 'Get detailed information for a specific bioassay by AID',
          inputSchema: {
            type: 'object',
            properties: {
              aid: { type: 'number', description: 'PubChem Assay ID (AID)' },
            },
            required: ['aid'],
          },
        },
        {
          name: 'get_compound_bioactivities',
          description: 'Get all bioassay results and activities for a compound',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
              activity_outcome: { type: 'string', enum: ['active', 'inactive', 'inconclusive', 'all'], description: 'Filter by activity outcome (default: all)' },
            },
            required: ['cid'],
          },
        },
        {
          name: 'search_by_target',
          description: 'Find compounds tested against a specific biological target',
          inputSchema: {
            type: 'object',
            properties: {
              target: { type: 'string', description: 'Target name (gene, protein, or pathway)' },
              activity_type: { type: 'string', description: 'Type of activity (e.g., IC50, EC50, Ki)' },
              max_records: { type: 'number', description: 'Maximum number of results (1-1000, default: 100)', minimum: 1, maximum: 1000 },
            },
            required: ['target'],
          },
        },
        {
          name: 'compare_activity_profiles',
          description: 'Compare bioactivity profiles across multiple compounds',
          inputSchema: {
            type: 'object',
            properties: {
              cids: { type: 'array', items: { type: 'number' }, description: 'Array of PubChem CIDs (2-50)', minItems: 2, maxItems: 50 },
              activity_type: { type: 'string', description: 'Specific activity type for comparison (optional)' },
            },
            required: ['cids'],
          },
        },
    
        // Safety & Toxicity (4 tools)
        {
          name: 'get_safety_data',
          description: 'Get GHS hazard classifications and safety information',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
            },
            required: ['cid'],
          },
        },
        {
          name: 'get_toxicity_info',
          description: 'Get toxicity data including LD50, carcinogenicity, and mutagenicity',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
            },
            required: ['cid'],
          },
        },
        {
          name: 'assess_environmental_fate',
          description: 'Assess environmental fate including biodegradation and bioaccumulation',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
            },
            required: ['cid'],
          },
        },
        {
          name: 'get_regulatory_info',
          description: 'Get regulatory information from FDA, EPA, and international agencies',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
            },
            required: ['cid'],
          },
        },
    
        // Cross-References & Integration (4 tools)
        {
          name: 'get_external_references',
          description: 'Get links to external databases (ChEMBL, DrugBank, KEGG, etc.)',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
            },
            required: ['cid'],
          },
        },
        {
          name: 'search_patents',
          description: 'Search for chemical patents and intellectual property information',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
              query: { type: 'string', description: 'Patent search query (alternative to CID)' },
            },
            required: [],
          },
        },
        {
          name: 'get_literature_references',
          description: 'Get PubMed citations and scientific literature references',
          inputSchema: {
            type: 'object',
            properties: {
              cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
            },
            required: ['cid'],
          },
        },
        {
          name: 'batch_compound_lookup',
          description: 'Process multiple compound IDs efficiently',
          inputSchema: {
            type: 'object',
            properties: {
              cids: { type: 'array', items: { type: 'number' }, description: 'Array of PubChem CIDs (1-200)', minItems: 1, maxItems: 200 },
              operation: { type: 'string', enum: ['property', 'synonyms', 'classification', 'description'], description: 'Operation to perform (default: property)' },
            },
            required: ['cids'],
          },
        },
      ],
    }));
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 information, implying a read-only operation, but lacks details on permissions, rate limits, response format, or error handling. This is a significant gap 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 is front-loaded and appropriately sized for its function, with no wasted information.

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 pharmacophore features and the lack of annotations and output schema, the description is insufficient. It does not explain what 'pharmacophore features' or 'binding site information' entail, the return format, or any behavioral traits, leaving the agent with inadequate context for 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 'cid' parameter clearly documented as 'PubChem Compound ID (CID)'. The description does not add any additional meaning beyond this, such as format examples or constraints, so it meets the baseline score 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 tool's purpose with a specific verb ('Get') and resources ('pharmacophore features and binding site information'), making it easy to understand what it does. However, it doesn't distinguish itself from sibling tools like 'get_3d_conformers' or 'get_compound_info' that also retrieve compound-related data, which prevents a perfect score.

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 tools available for compound data retrieval (e.g., 'get_compound_info', 'get_3d_conformers'), there is no indication of specific contexts, prerequisites, or exclusions for selecting this tool over others.

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/Augmented-Nature-PubChem-MCP-Server'

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