Skip to main content
Glama

calculate_descriptors

Calculate molecular descriptors and fingerprints for PubChem compounds to analyze chemical 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 that executes the tool logic for 'calculate_descriptors'. Currently a placeholder indicating it's not yet implemented.
    private async handleCalculateDescriptors(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Descriptor calculation not yet implemented', args }, null, 2) }] };
    }
  • src/index.ts:515-526 (registration)
    Registration of the 'calculate_descriptors' tool in the tools array passed to server.setTools(), 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 request handler switch statement that routes calls to the calculate_descriptors handler.
    case 'calculate_descriptors':
      return await this.handleCalculateDescriptors(args);
  • Input schema definition for validating arguments to the calculate_descriptors tool.
    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'],
    },
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 behavioral traits like computational intensity, rate limits, authentication needs, or what 'comprehensive' entails (e.g., output format, time to compute). This leaves gaps for an agent to understand operational implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for the tool's complexity, though it could be slightly more informative without losing conciseness.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'comprehensive' means in terms of output (e.g., types of descriptors, format), nor does it address behavioral aspects like performance or limitations, making it inadequate for an agent to fully understand the tool's 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?

Schema description coverage is 100%, so the schema already documents both parameters well. The description adds no additional meaning beyond the schema, such as explaining what 'descriptors and fingerprints' are or how 'comprehensive' relates to the 'descriptor_type' enum. 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 action ('calculate') and resource ('molecular descriptors and fingerprints'), making the purpose understandable. However, it doesn't differentiate from siblings like 'get_compound_properties' or 'predict_admet_properties' which might also involve molecular analysis, leaving room for confusion about when to choose this specific tool.

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 related to molecular analysis (e.g., 'get_compound_properties', 'predict_admet_properties'), there is no indication of context, prerequisites, or exclusions to help an agent select appropriately among them.

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