Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

calculate_descriptors

Compute molecular descriptors and fingerprints for chemical compounds using PubChem data to analyze molecular properties and structure.

Instructions

Calculate comprehensive molecular descriptors and fingerprints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)
descriptor_typeNoType of descriptors (default: all)

Implementation Reference

  • The main handler function for the 'calculate_descriptors' tool. It currently returns a placeholder message indicating that descriptor calculation is not yet implemented.
    private async handleCalculateDescriptors(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Descriptor calculation not yet implemented', args }, null, 2) }] };
    }
  • Input schema definition for the 'calculate_descriptors' tool, specifying parameters like CID and descriptor type.
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
        descriptor_type: { type: 'string', enum: ['all', 'basic', 'topological', '3d'], description: 'Type of descriptors (default: all)' },
      },
      required: ['cid'],
    },
  • src/index.ts:515-526 (registration)
    Registration of the 'calculate_descriptors' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'calculate_descriptors',
      description: 'Calculate comprehensive molecular descriptors and fingerprints',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
          descriptor_type: { type: 'string', enum: ['all', 'basic', 'topological', '3d'], description: 'Type of descriptors (default: all)' },
        },
        required: ['cid'],
      },
    },
  • src/index.ts:768-769 (registration)
    Dispatch case in the CallToolRequest handler that routes 'calculate_descriptors' calls to the specific handler method.
    case 'calculate_descriptors':
      return await this.handleCalculateDescriptors(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'comprehensive' but doesn't disclose computational cost, time, rate limits, or output format. For a calculation tool, this lack of behavioral context 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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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 calculation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'descriptors and fingerprints' entail, potential limitations, or return values, leaving key contextual gaps for effective agent 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 already documents both parameters well. The description adds no additional meaning beyond implying 'comprehensive' might relate to 'descriptor_type', but this is minimal. 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 clearly states the verb 'calculate' and the resource 'molecular descriptors and fingerprints', making the purpose understandable. However, it doesn't distinguish this tool from siblings like 'get_compound_properties' or 'predict_admet_properties' that might also compute molecular characteristics, missing specific differentiation.

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 molecular analysis, there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool names 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/Augmented-Nature/Augmented-Nature-PubChem-MCP-Server'

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