Skip to main content
Glama

get_compound_bioactivities

Retrieve bioassay results and activity data for chemical compounds from PubChem to analyze biological effects and experimental outcomes.

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 main handler function for executing the 'get_compound_bioactivities' tool. Currently implemented as a placeholder that returns a 'not yet implemented' message.
    private async handleGetCompoundBioactivities(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Bioactivity search not yet implemented', args }, null, 2) }] };
    }
  • Input schema defining the parameters for the 'get_compound_bioactivities' tool: requires 'cid', optional 'activity_outcome'.
    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:600-611 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input 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'],
      },
    },
  • src/index.ts:784-785 (registration)
    Dispatch registration in the main CallToolRequestSchema switch statement that calls the handler.
    case 'get_compound_bioactivities':
      return await this.handleGetCompoundBioactivities(args);
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 retrieving data but lacks details on permissions, rate limits, pagination, or response format. For a data-fetching tool with zero annotation coverage, this is a significant gap in transparency.

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 is front-loaded and wastes no space, making it highly concise and well-structured for quick comprehension.

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 absence of annotations and output schema, the description is incomplete. It does not address behavioral aspects like data format, limitations, or error handling. For a tool with two parameters and no structured output information, more context is needed to ensure reliable agent usage.

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 input schema already documents both parameters ('cid' and 'activity_outcome') with descriptions and an enum. The description adds no additional meaning beyond implying filtering by activity outcome, which is already covered in the schema, resulting in a baseline score of 3.

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 resource ('all bioassay results and activities for a compound'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'search_bioassays' or 'compare_activity_profiles', which could provide similar or overlapping functionality, leaving room for ambiguity in tool selection.

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 sibling tools such as 'search_bioassays' and 'compare_activity_profiles', there is no indication of context, prerequisites, or exclusions, leaving the agent to infer usage without explicit direction.

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