Skip to main content
Glama
Augmented-Nature

PubChem MCP Server

superstructure_search

Identify larger chemical compounds containing a specific query structure. Input a SMILES string to retrieve up to 10,000 results, aiding in chemical analysis and compound exploration through the PubChem database.

Instructions

Find larger compounds that contain the query structure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_recordsNoMaximum number of results (1-10000, default: 100)
smilesYesSMILES string of the query structure

Implementation Reference

  • The handler function that implements the logic for the 'superstructure_search' tool. Currently, it is a placeholder that returns a message indicating the feature is not yet implemented.
    private async handleSuperstructureSearch(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Superstructure search not yet implemented', args }, null, 2) }] };
    }
  • The input schema definition for the 'superstructure_search' tool, specifying the expected parameters: smiles (required string) and optional max_records (number).
    inputSchema: {
      type: 'object',
      properties: {
        smiles: { type: 'string', description: 'SMILES string of the query structure' },
        max_records: { type: 'number', description: 'Maximum number of results (1-10000, default: 100)', minimum: 1, maximum: 10000 },
      },
      required: ['smiles'],
    },
  • src/index.ts:466-477 (registration)
    The registration of the 'superstructure_search' tool in the tools list returned by ListToolsRequestSchema, including name, description, and input schema.
    {
      name: 'superstructure_search',
      description: 'Find larger compounds that contain the query structure',
      inputSchema: {
        type: 'object',
        properties: {
          smiles: { type: 'string', description: 'SMILES string of the query structure' },
          max_records: { type: 'number', description: 'Maximum number of results (1-10000, default: 100)', minimum: 1, maximum: 10000 },
        },
        required: ['smiles'],
      },
    },
  • src/index.ts:758-759 (registration)
    Switch case in the CallToolRequestSchema handler that routes calls to the specific superstructure_search handler function.
    case 'superstructure_search':
      return await this.handleSuperstructureSearch(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical behavioral details: it doesn't specify if this is a read-only operation, what the output format is, whether there are rate limits, authentication needs, or how results are ordered/returned. For a search tool with no annotation coverage, this is a significant gap.

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 purpose with zero waste. It's appropriately sized and front-loaded, 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 complexity of a search tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'larger compounds' means in context, how results are returned, or any behavioral traits, leaving the agent with insufficient information to fully understand the tool's operation.

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%, with both parameters well-documented in the schema (SMILES string and max_records with range/default). The description adds no additional parameter semantics beyond implying the query structure is input via SMILES, so it meets the baseline of 3 where 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 verb 'find' and the resource 'larger compounds that contain the query structure', making the purpose specific and understandable. It distinguishes from siblings like 'substructure_search' (which likely finds smaller compounds) by specifying 'larger compounds', but doesn't explicitly name alternatives or fully differentiate from all siblings like 'search_similar_compounds'.

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 when-not scenarios, prerequisites, or explicitly name sibling tools like 'substructure_search' or 'search_similar_compounds' for comparison, leaving the agent to infer usage from the purpose 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

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