Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

superstructure_search

Search PubChem for compounds containing a specific molecular structure using SMILES input to identify larger chemical entities.

Instructions

Find larger compounds that contain the query structure

Input Schema

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

Implementation Reference

  • The handler function for 'superstructure_search' tool. Currently a placeholder that returns a 'not yet implemented' message.
    private async handleSuperstructureSearch(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Superstructure search not yet implemented', args }, null, 2) }] };
    }
  • Input schema definition for the superstructure_search tool, specifying parameters like smiles (required) and max_records.
    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)
    Registration of the superstructure_search tool in the ListTools response, 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)
    Dispatch/registration in the CallToolRequestSchema switch statement that routes to the handler.
    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 mentions 'Find larger compounds' but doesn't specify aspects like rate limits, authentication needs, or what 'larger' means in terms of size or complexity. This leaves gaps in understanding the tool's behavior beyond basic functionality.

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 without unnecessary words. It is front-loaded and earns its place by conveying the core functionality clearly.

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' entails, how results are returned, or any behavioral traits, making it inadequate for full agent understanding in this context.

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, so parameters are well-documented there. The description adds no additional meaning beyond implying the 'smiles' parameter is for querying and 'max_records' limits results, but this is already covered in the schema. Baseline score of 3 is appropriate as the schema handles 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 understandable. However, it doesn't explicitly differentiate from the sibling tool 'substructure_search,' which might have overlapping functionality, leaving some ambiguity about uniqueness.

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 is provided on when to use this tool versus alternatives like 'substructure_search' or other search tools in the list. The description implies usage for finding larger compounds but lacks context on prerequisites, exclusions, or specific 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

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

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