Skip to main content
Glama

compare_activity_profiles

Compare bioactivity profiles across multiple PubChem compounds to identify similarities and differences in their biological effects.

Instructions

Compare bioactivity profiles across multiple compounds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidsYesArray of PubChem CIDs (2-50)
activity_typeNoSpecific activity type for comparison (optional)

Implementation Reference

  • The main handler function for the 'compare_activity_profiles' tool. It currently returns a placeholder response indicating the feature is not yet implemented.
    private async handleCompareActivityProfiles(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Activity profile comparison not yet implemented', args }, null, 2) }] };
    }
  • Input schema defining the expected parameters for the tool: an array of PubChem CIDs (required, 2-50) and optional activity_type.
    inputSchema: {
      type: 'object',
      properties: {
        cids: { type: 'array', items: { type: 'number' }, description: 'Array of PubChem CIDs (2-50)', minItems: 2, maxItems: 50 },
        activity_type: { type: 'string', description: 'Specific activity type for comparison (optional)' },
      },
      required: ['cids'],
    },
  • src/index.ts:788-789 (registration)
    Registration and dispatch logic in the CallToolRequestSchema handler's switch statement, which calls the tool handler.
    case 'compare_activity_profiles':
      return await this.handleCompareActivityProfiles(args);
  • src/index.ts:625-637 (registration)
    Tool registration in the ListToolsRequestSchema response, including name, description, and input schema.
    {
      name: 'compare_activity_profiles',
      description: 'Compare bioactivity profiles across multiple compounds',
      inputSchema: {
        type: 'object',
        properties: {
          cids: { type: 'array', items: { type: 'number' }, description: 'Array of PubChem CIDs (2-50)', minItems: 2, maxItems: 50 },
          activity_type: { type: 'string', description: 'Specific activity type for comparison (optional)' },
        },
        required: ['cids'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose what 'compare' entails (e.g., output format, computational intensity, rate limits, or authentication needs). The description is minimal and doesn't add context beyond the basic action, leaving the agent with insufficient information about how the tool behaves.

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 wasted words. It front-loads the core purpose ('compare bioactivity profiles') and is appropriately sized for the tool's complexity, 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 no annotations and no output schema, the description is incomplete. It doesn't explain what the comparison yields (e.g., similarity scores, visualizations, or tabular data), which is critical for a tool with 2 parameters and bioactivity analysis complexity. The description lacks necessary context 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 fully documents parameters (cids as PubChem CIDs array with constraints, activity_type as optional string). The description adds no additional parameter semantics beyond implying comparison involves bioactivity profiles, which is already inferred from the tool name and schema. 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 ('compare') and target ('bioactivity profiles across multiple compounds'), which is specific and unambiguous. It distinguishes from siblings like 'get_compound_bioactivities' (which retrieves rather than compares) and 'search_bioassays' (which searches rather than compares profiles), though it doesn't explicitly name these distinctions.

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 prerequisites (e.g., needing PubChem CIDs from other tools), exclusions, or comparative contexts with siblings like 'get_compound_bioactivities' for single-compound data or 'search_bioassays' for assay-based searches.

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