Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

search_bioassays

Find biological assays by target protein, gene name, description, or data source to support chemical research and analysis.

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 logic for the 'search_bioassays' tool. Currently implemented as a placeholder returning a 'not yet implemented' message.
    private async handleSearchBioassays(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Bioassay search not yet implemented', args }, null, 2) }] };
    }
  • src/index.ts:576-587 (registration)
    Registration of the 'search_bioassays' tool in the tools array passed to server.setTools(), including name, description, and input 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: [],
    },
  • 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: [],
  • Switch case in the main request handler that dispatches calls to the 'search_bioassays' 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?

No annotations are provided, so the description carries full burden. It mentions searchable fields but lacks behavioral details: no indication of read-only vs. mutation, authentication needs, rate limits, pagination, result format, or error handling. For a search tool with zero annotation coverage, this is a significant gap.

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?

Single sentence, front-loaded with core purpose, zero waste. Efficiently conveys the tool's function 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?

Given no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't address result format, limitations, or how it differs from similar tools like get_assay_info, leaving the agent with insufficient context for effective 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 already documents all four parameters thoroughly. The description adds minimal value by listing searchable attributes (target, description, source) but doesn't explain parameter interactions, precedence, or provide examples beyond schema details.

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 'search' and resource 'biological assays', specifying searchable attributes (target, description, source). It distinguishes from most siblings (e.g., search_compounds, search_by_target) by focusing on assays rather than compounds or patents, though differentiation from get_assay_info is less explicit.

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?

No explicit guidance on when to use this tool versus alternatives like search_by_target, get_assay_info, or get_compound_bioactivities. The description implies usage for searching assays by multiple criteria but doesn't specify scenarios, prerequisites, or exclusions.

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