Skip to main content
Glama

get_3d_conformers

Retrieve 3D molecular conformer data and structural information from PubChem's chemical database using compound IDs for molecular modeling and analysis.

Instructions

Get 3D conformer data and structural information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)
conformer_typeNoType of conformer data (default: 3d)

Implementation Reference

  • The main handler function that implements the logic for the 'get_3d_conformers' tool by validating input and fetching 3D conformer properties (Volume3D, ConformerCount3D) from the PubChem API.
    private async handleGet3dConformers(args: any) {
      if (!isValidConformerArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid 3D conformer arguments');
      }
    
      try {
        const response = await this.apiClient.get(`/compound/cid/${args.cid}/property/Volume3D,ConformerCount3D/JSON`);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                cid: args.cid,
                conformer_type: args.conformer_type || '3d',
                properties: response.data,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get 3D conformers: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • The input schema definition for the 'get_3d_conformers' tool, registered in the tools list.
    {
      name: 'get_3d_conformers',
      description: 'Get 3D conformer data and structural information',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
          conformer_type: { type: 'string', enum: ['3d', '2d'], description: 'Type of conformer data (default: 3d)' },
        },
        required: ['cid'],
      },
    },
  • Helper function for validating the input arguments specific to the 'get_3d_conformers' tool.
    const isValidConformerArgs = (
      args: any
    ): args is { cid: number | string; conformer_type?: string } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        (typeof args.cid === 'number' || typeof args.cid === 'string') &&
        (args.conformer_type === undefined || ['3d', '2d'].includes(args.conformer_type))
      );
    };
  • src/index.ts:760-761 (registration)
    Registration of the 'get_3d_conformers' handler in the main tool dispatcher switch statement.
    case 'get_3d_conformers':
      return await this.handleGet3dConformers(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 mentions retrieving data but lacks details on permissions, rate limits, response format, or error handling. For a tool with no 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 that directly states the tool's function without unnecessary words. It is front-loaded and wastes no space, 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 returned data includes (e.g., file formats, structural details) or behavioral aspects like error cases. 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 schema description coverage is 100%, with clear descriptions for both parameters (CID and conformer_type). The description adds no additional meaning beyond the schema, such as explaining what '3D conformer data' entails or how the CID is used. 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 action ('Get') and the resource ('3D conformer data and structural information'), making the purpose understandable. However, it doesn't differentiate this tool from potential siblings like 'get_compound_info' or 'calculate_descriptors' that might also provide structural 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. Given the many sibling tools for compound analysis (e.g., 'get_compound_info', 'calculate_descriptors'), there is no indication of specific use cases, prerequisites, or exclusions, leaving 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/k-lordbodin7/PubChem-MCP-Server'

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