Skip to main content
Glama

get_pharmacophore_features

Extract pharmacophore features and binding site data for PubChem compounds to analyze molecular interactions and drug design potential.

Instructions

Get pharmacophore features and binding site information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)

Implementation Reference

  • The handler function that implements the core logic for the 'get_pharmacophore_features' tool. Currently a placeholder indicating not yet implemented.
    private async handleGetPharmacophoreFeatures(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Pharmacophore features not yet implemented', args }, null, 2) }] };
    }
  • src/index.ts:562-572 (registration)
    Tool registration in the ListToolsRequestSchema response, including name, description, and input schema definition.
    {
      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)
    Dispatcher case in the CallToolRequestSchema handler that routes calls to the tool's handler function.
    case 'get_pharmacophore_features':
      return await this.handleGetPharmacophoreFeatures(args);
  • Input schema definition for validating tool arguments (CID required).
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
      },
      required: ['cid'],
    },
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 but doesn't specify whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple retrieval with one parameter) and high schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it lacks details on behavioral traits and return values, which could be important for an AI agent to use it correctly.

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 (the 'cid' parameter is documented as 'PubChem Compound ID (CID)'), so the baseline is 3. The description adds no additional parameter information beyond what the schema provides, such as format details or examples, but it doesn't need to compensate for gaps.

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: 'Get pharmacophore features and binding site information' - a specific verb ('Get') and resources ('pharmacophore features', 'binding site information'). It distinguishes from most siblings that focus on different chemical analyses (e.g., 'analyze_molecular_complexity', 'calculate_descriptors'), though it doesn't explicitly differentiate from similar retrieval tools like 'get_compound_info' or 'get_3d_conformers'.

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, context, or exclusions, nor does it reference any sibling tools for comparison. The agent must infer usage from the tool name and description 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/k-lordbodin7/PubChem-MCP-Server'

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