Skip to main content
Glama
Augmented-Nature

PubChem MCP Server

search_compounds

Search the PubChem database for chemical compounds using names, CAS numbers, formulas, or identifiers to retrieve relevant results efficiently.

Instructions

Search PubChem database for compounds by name, CAS number, formula, or identifier

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_recordsNoMaximum number of results (1-10000, default: 100)
queryYesSearch query (compound name, CAS, formula, or identifier)
search_typeNoType of search to perform (default: name)

Implementation Reference

  • The main handler function that executes the search_compounds tool. Validates input, queries PubChem API for CIDs by name/SMILES/etc., fetches details for top results, and returns formatted JSON response.
    private async handleSearchCompounds(args: any) {
      if (!isValidCompoundSearchArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid compound search arguments');
      }
    
      try {
        const searchType = args.search_type || 'name';
        const maxRecords = args.max_records || 100;
    
        const response = await this.apiClient.get(`/compound/${searchType}/${encodeURIComponent(args.query)}/cids/JSON`, {
          params: {
            MaxRecords: maxRecords,
          },
        });
    
        if (response.data?.IdentifierList?.CID?.length > 0) {
          const cids = response.data.IdentifierList.CID.slice(0, 10);
          const detailsResponse = await this.apiClient.get(`/compound/cid/${cids.join(',')}/property/MolecularFormula,MolecularWeight,CanonicalSMILES,IUPACName/JSON`);
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify({
                  query: args.query,
                  search_type: searchType,
                  total_found: response.data.IdentifierList.CID.length,
                  details: detailsResponse.data,
                }, null, 2),
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ message: 'No compounds found', query: args.query }, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to search compounds: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Tool registration entry in ListToolsRequestSchema handler, defining the tool name, description, and input schema for validation.
      name: 'search_compounds',
      description: 'Search PubChem database for compounds by name, CAS number, formula, or identifier',
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'Search query (compound name, CAS, formula, or identifier)' },
          search_type: { type: 'string', enum: ['name', 'smiles', 'inchi', 'sdf', 'cid', 'formula'], description: 'Type of search to perform (default: name)' },
          max_records: { type: 'number', description: 'Maximum number of results (1-10000, default: 100)', minimum: 1, maximum: 10000 },
        },
        required: ['query'],
      },
    },
  • Type guard function for validating input arguments to the search_compounds tool.
    const isValidCompoundSearchArgs = (
      args: any
    ): args is { query: string; search_type?: string; max_records?: number } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        typeof args.query === 'string' &&
        args.query.length > 0 &&
        (args.search_type === undefined || ['name', 'smiles', 'inchi', 'sdf', 'cid', 'formula'].includes(args.search_type)) &&
        (args.max_records === undefined || (typeof args.max_records === 'number' && args.max_records > 0 && args.max_records <= 10000))
      );
    };
  • src/index.ts:740-741 (registration)
    Switch case in CallToolRequestSchema handler that routes execution to the search_compounds handler function.
    case 'search_compounds':
      return await this.handleSearchCompounds(args);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't mention rate limits, authentication needs, response format, pagination, or error handling. 'Search' implies read-only, but this isn't explicitly stated, leaving gaps 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?

Single sentence, front-loaded with the core action, zero waste. Every word earns its place by specifying the database, target, and searchable fields efficiently.

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?

For a search tool with no annotations and no output schema, the description is incomplete. It doesn't explain what results look like (e.g., compound IDs, names, properties), how many results are typical, or handling of large result sets, leaving significant gaps for an AI agent to use it effectively.

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 parameters are well-documented in the schema. The description adds minimal value by listing searchable fields, which aligns with the 'query' parameter and 'search_type' enum, but doesn't provide additional syntax or format details beyond what the schema already covers.

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 verb 'search' and resource 'PubChem database for compounds', specifying the searchable fields (name, CAS number, formula, or identifier). It distinguishes from siblings like 'search_by_cas_number' or 'search_by_smiles' by being a general search tool, but doesn't explicitly contrast them.

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?

No guidance on when to use this tool versus alternatives like 'search_by_cas_number', 'search_by_smiles', or 'batch_compound_lookup'. The description lists searchable fields but doesn't explain trade-offs or recommend specific tools for different scenarios.

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

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

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