Skip to main content
Glama

superstructure_search

Search PubChem for compounds containing a specific chemical structure by providing its SMILES string. Returns larger molecules that include the query structure as a substructure.

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 the 'superstructure_search' tool. It currently returns a placeholder response 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) }] };
    }
  • src/index.ts:466-477 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      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)
    Dispatcher case in the CallToolRequestSchema handler that routes calls to the superstructure_search handler.
    case 'superstructure_search':
      return await this.handleSuperstructureSearch(args);
  • Input schema definition for the superstructure_search tool, specifying parameters like smiles 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'],
    },
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. It mentions that the tool finds 'larger compounds,' implying a search operation, but does not describe what 'larger' entails, how results are returned (e.g., format, pagination), or any limitations (e.g., performance, data sources). For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence with no wasted words. It is front-loaded with the core purpose and efficiently conveys the tool's function. Every part of the sentence earns its place.

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 lacks details on what 'larger compounds' means, how results are structured, any limitations (e.g., database scope), or error handling. The agent has insufficient context to use the tool effectively beyond basic parameter input.

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 both parameters ('smiles' and 'max_records'). The description does not add any meaning beyond what the schema provides—it does not explain parameter interactions, default behaviors, or usage examples. Baseline 3 is appropriate when 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 tool's purpose: 'Find larger compounds that contain the query structure.' It specifies the action ('Find') and the resource ('larger compounds'), and distinguishes it from sibling tools like 'substructure_search' (which likely finds compounds containing the query) and 'search_similar_compounds' (which likely finds similar compounds). However, it could be more specific about what 'larger' means (e.g., in terms of molecular size or complexity).

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 does not mention sibling tools like 'substructure_search' or 'search_similar_compounds', nor does it specify use cases, prerequisites, or exclusions. The agent must infer usage from the tool name and description 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

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