Skip to main content
Glama

get_compound_properties

Retrieve molecular properties like molecular weight, logP, and TPSA for chemical compounds using PubChem Compound IDs. Specify optional properties to get targeted data from PubChem's chemical database.

Instructions

Get molecular properties (MW, logP, TPSA, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)
propertiesNoSpecific properties to retrieve (optional)

Implementation Reference

  • The handler function that executes the get_compound_properties tool. Validates input using isValidPropertiesArgs, fetches specified molecular properties from PubChem API for the given CID, and returns the JSON response.
    private async handleGetCompoundProperties(args: any) {
      if (!isValidPropertiesArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid compound properties arguments');
      }
    
      try {
        const properties = args.properties || [
          'MolecularWeight', 'XLogP', 'TPSA', 'HBondDonorCount', 'HBondAcceptorCount',
          'RotatableBondCount', 'Complexity', 'HeavyAtomCount', 'Charge'
        ];
    
        const response = await this.apiClient.get(`/compound/cid/${args.cid}/property/${properties.join(',')}/JSON`);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get compound properties: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Input schema definition for the get_compound_properties tool provided in the ListTools response.
    {
      name: 'get_compound_properties',
      description: 'Get molecular properties (MW, logP, TPSA, etc.)',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
          properties: { type: 'array', items: { type: 'string' }, description: 'Specific properties to retrieve (optional)' },
        },
        required: ['cid'],
      },
    },
  • src/index.ts:766-767 (registration)
    Registration in the CallToolRequestSchema switch dispatcher, routing calls to the handler method.
    case 'get_compound_properties':
      return await this.handleGetCompoundProperties(args);
  • Type guard helper function used to validate arguments for the get_compound_properties tool.
    const isValidPropertiesArgs = (
      args: any
    ): args is { cid: number | string; properties?: string[] } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        (typeof args.cid === 'number' || typeof args.cid === 'string') &&
        (args.properties === undefined || (Array.isArray(args.properties) && args.properties.every((p: any) => typeof p === 'string')))
      );
    };
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. While 'Get' implies a read-only operation, the description doesn't specify whether this requires authentication, has rate limits, returns structured data, or handles errors. For a tool with no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool, though it could be slightly more informative without losing conciseness.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral traits, and output format. With no output schema, the description doesn't explain what values are returned, leaving gaps for an AI agent.

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, clearly documenting both parameters (cid and properties). The description adds minimal value beyond the schema by mentioning example property types (MW, logP, TPSA), which helps clarify what 'properties' might include, but doesn't provide additional syntax or format details. Baseline 3 is appropriate when the schema does most of the work.

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 ('molecular properties'), and provides examples of the types of properties (MW, logP, TPSA). However, it doesn't explicitly differentiate this tool from similar siblings like 'calculate_descriptors' or 'get_compound_info', which might also retrieve molecular properties.

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 (e.g., 'calculate_descriptors', 'get_compound_info', 'predict_admet_properties'), there's no indication of whether this tool is for basic property retrieval, how it differs from descriptors calculation, or any prerequisites for use.

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