Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

search_by_target

Find chemical compounds tested against specific biological targets like genes or proteins, with activity data such as IC50 values from PubChem's database.

Instructions

Find compounds tested against a specific biological target

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget name (gene, protein, or pathway)
activity_typeNoType of activity (e.g., IC50, EC50, Ki)
max_recordsNoMaximum number of results (1-1000, default: 100)

Implementation Reference

  • The primary handler function implementing the 'search_by_target' tool logic. It is a placeholder that returns a 'not yet implemented' message with the input arguments.
    private async handleSearchByTarget(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Target search not yet implemented', args }, null, 2) }] };
    }
  • src/index.ts:612-623 (registration)
    Registration of the 'search_by_target' tool in the ListToolsRequestSchema handler, including its name, description, and input schema definition.
    {
      name: 'search_by_target',
      description: 'Find compounds tested against a specific biological target',
      inputSchema: {
        type: 'object',
        properties: {
          target: { type: 'string', description: 'Target name (gene, protein, or pathway)' },
          activity_type: { type: 'string', description: 'Type of activity (e.g., IC50, EC50, Ki)' },
          max_records: { type: 'number', description: 'Maximum number of results (1-1000, default: 100)', minimum: 1, maximum: 1000 },
        },
        required: ['target'],
      },
  • The input schema defining the expected parameters for the 'search_by_target' tool.
    inputSchema: {
      type: 'object',
      properties: {
        target: { type: 'string', description: 'Target name (gene, protein, or pathway)' },
        activity_type: { type: 'string', description: 'Type of activity (e.g., IC50, EC50, Ki)' },
        max_records: { type: 'number', description: 'Maximum number of results (1-1000, default: 100)', minimum: 1, maximum: 1000 },
      },
      required: ['target'],
    },
  • src/index.ts:786-787 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes calls to the 'search_by_target' tool to its handler function.
    case 'search_by_target':
      return await this.handleSearchByTarget(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 'Find compounds tested against a specific biological target,' implying a read-only search operation, but fails to detail critical aspects like response format, pagination, rate limits, authentication needs, or potential side effects. For a 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: 'Find compounds tested against a specific biological target.' It is front-loaded with the core purpose, contains no redundant information, and is appropriately sized for the tool's complexity, making it highly concise and well-structured.

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 the tool's moderate complexity (3 parameters, 1 required), 100% schema coverage, and no output schema, the description is minimally adequate. It states the purpose clearly but lacks behavioral details and usage guidelines, which are crucial for effective tool invocation. The absence of annotations and output schema means the description should compensate more, but it falls short, resulting in a baseline score.

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%, meaning the input schema already documents all parameters thoroughly. The description does not add any semantic details beyond what the schema provides, such as examples or contextual usage for parameters. However, it implicitly reinforces the primary parameter 'target' by mentioning it in the description, aligning with the baseline score when schema coverage is high.

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: 'Find compounds tested against a specific biological target.' It specifies the verb ('Find'), resource ('compounds'), and scope ('tested against a specific biological target'), which is precise and actionable. However, it doesn't explicitly differentiate from sibling tools like 'search_compounds' or 'search_bioassays,' which might have overlapping functionality, preventing a perfect score.

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 lacks context about prerequisites, exclusions, or comparisons to sibling tools such as 'search_bioassays' or 'get_compound_bioactivities,' which could be related. This omission leaves the agent without clear direction for tool selection.

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