Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

get_compound_bioactivities

Retrieve bioassay results and activity data for chemical compounds from PubChem to analyze compound effects in biological tests.

Instructions

Get all bioassay results and activities for a compound

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)
activity_outcomeNoFilter by activity outcome (default: all)

Implementation Reference

  • The handler function that executes the 'get_compound_bioactivities' tool logic. Currently implemented as a placeholder indicating that full bioactivity search is not yet implemented.
    private async handleGetCompoundBioactivities(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Bioactivity search not yet implemented', args }, null, 2) }] };
    }
  • Input schema definition for the 'get_compound_bioactivities' tool, specifying parameters like CID and optional activity outcome filter.
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
        activity_outcome: { type: 'string', enum: ['active', 'inactive', 'inconclusive', 'all'], description: 'Filter by activity outcome (default: all)' },
      },
      required: ['cid'],
    },
  • src/index.ts:784-785 (registration)
    Registration and dispatch case in the main CallToolRequestSchema switch statement that routes calls to the handler.
    case 'get_compound_bioactivities':
      return await this.handleGetCompoundBioactivities(args);
  • src/index.ts:600-610 (registration)
    Tool registration entry in the ListToolsRequestSchema response, including name, description, and schema.
    {
      name: 'get_compound_bioactivities',
      description: 'Get all bioassay results and activities for a compound',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
          activity_outcome: { type: 'string', enum: ['active', 'inactive', 'inconclusive', 'all'], description: 'Filter by activity outcome (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 the full burden of behavioral disclosure. It states 'Get all bioassay results and activities', implying a read-only operation, but doesn't specify details like data format, pagination, rate limits, or permissions required. For a tool with no annotations, this is inadequate, scoring a 2 for vague behavioral information.

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's front-loaded and appropriately sized, earning a 5 for optimal conciseness and structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 2 parameters with full schema coverage, the description is minimally complete. It covers the basic purpose but lacks details on behavior, output format, or usage context. For a simple read tool, it's adequate but has clear gaps, scoring a 3.

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%, with clear descriptions for both parameters (cid and activity_outcome). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or usage examples. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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 'Get' and the resource 'all bioassay results and activities for a compound', making the purpose specific and understandable. It distinguishes from siblings like 'get_compound_info' or 'search_bioassays' by focusing on bioassay results for a specific compound, though it doesn't explicitly name alternatives. This earns a 4 for being clear but lacking explicit sibling 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. It doesn't mention prerequisites, context, or exclusions, such as how it differs from 'search_bioassays' or 'compare_activity_profiles'. With no usage instructions, it scores a 2 for minimal guidance.

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