Skip to main content
Glama

batch_compound_lookup

Retrieve chemical properties, synonyms, classifications, or descriptions for up to 200 PubChem compounds simultaneously to streamline chemical data analysis.

Instructions

Process multiple compound IDs efficiently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidsYesArray of PubChem CIDs (1-200)
operationNoOperation to perform (default: property)

Implementation Reference

  • The main handler function that executes the batch_compound_lookup tool logic. It validates input, fetches properties (MolecularWeight, CanonicalSMILES, IUPACName) for up to 10 CIDs from PubChem API, and returns results or errors.
    private async handleBatchCompoundLookup(args: any) {
      if (!isValidBatchArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid batch arguments');
      }
    
      try {
        const results = [];
        for (const cid of args.cids.slice(0, 10)) {
          try {
            const response = await this.apiClient.get(`/compound/cid/${cid}/property/MolecularWeight,CanonicalSMILES,IUPACName/JSON`);
            results.push({ cid, data: response.data, success: true });
          } catch (error) {
            results.push({ cid, error: error instanceof Error ? error.message : 'Unknown error', success: false });
          }
        }
    
        return { content: [{ type: 'text', text: JSON.stringify({ batch_results: results }, null, 2) }] };
      } catch (error) {
        throw new McpError(ErrorCode.InternalError, `Batch lookup failed: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Input schema definition for the batch_compound_lookup tool, specifying cids array (1-200 numbers) and optional operation enum.
    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'],
    },
  • src/index.ts:719-730 (registration)
    Registration of the batch_compound_lookup tool in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      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'],
      },
    },
  • src/index.ts:808-809 (registration)
    Dispatcher case in CallToolRequestSchema handler that routes batch_compound_lookup calls to the handler function.
    case 'batch_compound_lookup':
      return await this.handleBatchCompoundLookup(args);
  • Type guard and validation function for batch_compound_lookup arguments, matching the input schema.
    const isValidBatchArgs = (
      args: any
    ): args is { cids: number[]; operation?: string } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        Array.isArray(args.cids) &&
        args.cids.length > 0 &&
        args.cids.length <= 200 &&
        args.cids.every((cid: any) => typeof cid === 'number' && cid > 0) &&
        (args.operation === undefined || ['property', 'synonyms', 'classification', 'description'].includes(args.operation))
      );
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. 'Process' is vague about behavior—it doesn't specify what operations are performed, what data is returned, or any constraints like rate limits or authentication needs. 'Efficiently' hints at performance but lacks concrete details. For a tool with 2 parameters and no output schema, 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero waste—'Process multiple compound IDs efficiently' is front-loaded and appropriately sized. Every word contributes to the core message without redundancy or fluff, making it easy 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 2 parameters, no annotations, no output schema, and many sibling tools, the description is incomplete. It doesn't explain what 'process' entails operationally, what results to expect, or how it differs from similar tools. For a batch tool in a complex domain like compound analysis, 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?

Schema description coverage is 100%, so the schema fully documents parameters (cids array with limits, operation enum). The description adds no parameter-specific semantics beyond implying batch processing for 'multiple compound IDs', which aligns with the cids parameter but doesn't provide additional context like format examples or default behavior nuances. Baseline 3 is appropriate 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 'Process multiple compound IDs efficiently' clearly states the verb ('process') and resource ('multiple compound IDs'), and the 'efficiently' hint suggests batch processing. However, it doesn't distinguish this from sibling tools like 'get_compound_info' or 'get_compound_properties' that might handle single compounds, leaving some ambiguity about when to choose batch over individual lookups.

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 for compound-related operations (e.g., 'get_compound_properties', 'get_compound_synonyms'), there's no indication that this is the batch version or when batch processing is preferred over individual calls. The implicit context is efficiency for multiple IDs, but no explicit when/when-not rules are stated.

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