Skip to main content
Glama

search_bioassays

Find biological assays by target protein, gene name, description, or data source to access bioactivity data from PubChem's chemical database.

Instructions

Search for biological assays by target, description, or source

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoGeneral search query
targetNoTarget protein or gene name
sourceNoData source (e.g., ChEMBL, NCGC)
max_recordsNoMaximum number of results (1-1000, default: 100)

Implementation Reference

  • The handler function that executes the 'search_bioassays' tool logic. Currently implemented as a placeholder indicating it's not yet fully implemented.
    private async handleSearchBioassays(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Bioassay search not yet implemented', args }, null, 2) }] };
    }
  • The input schema definition for the 'search_bioassays' tool, defining parameters like query, target, source, and max_records.
    inputSchema: {
      type: 'object',
      properties: {
        query: { type: 'string', description: 'General search query' },
        target: { type: 'string', description: 'Target protein or gene name' },
        source: { type: 'string', description: 'Data source (e.g., ChEMBL, NCGC)' },
        max_records: { type: 'number', description: 'Maximum number of results (1-1000, default: 100)', minimum: 1, maximum: 1000 },
      },
      required: [],
    },
  • src/index.ts:575-588 (registration)
    The tool registration in the ListTools response, including name, description, and schema.
    {
      name: 'search_bioassays',
      description: 'Search for biological assays by target, description, or source',
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'General search query' },
          target: { type: 'string', description: 'Target protein or gene name' },
          source: { type: 'string', description: 'Data source (e.g., ChEMBL, NCGC)' },
          max_records: { type: 'number', description: 'Maximum number of results (1-1000, default: 100)', minimum: 1, maximum: 1000 },
        },
        required: [],
      },
    },
  • src/index.ts:780-781 (registration)
    The switch case registration in the CallToolRequest handler that dispatches to the specific handler function.
    case 'search_bioassays':
      return await this.handleSearchBioassays(args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It mentions what can be searched (target, description, source) but doesn't describe the search behavior, result format, pagination, rate limits, authentication requirements, or what happens when multiple parameters are combined. This is inadequate for a search tool with zero annotation coverage.

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 no wasted words. It's appropriately sized for a search tool and gets straight to the point 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 search tool with 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain result format, error conditions, or how multiple search parameters interact. Given the complexity of biological assay data and the lack of structured behavioral information, the description should provide more context about what users can expect from this search operation.

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?

The description mentions three searchable fields (target, description, source) that correspond to three of the four parameters, but doesn't explain the 'query' parameter or how parameters interact. With 100% schema description coverage, the schema already documents all parameters well, so the description adds only marginal value beyond what's in the structured schema.

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 tool's purpose as searching for biological assays using specific criteria (target, description, or source), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'search_by_target' or 'search_compounds,' leaving some ambiguity about when to choose this tool over those alternatives.

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 multiple search-related sibling tools (search_by_target, search_compounds, search_similar_compounds, etc.), there's no indication of this tool's specific use case, prerequisites, or how it differs from other search options.

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