Skip to main content
Glama
Augmented-Nature

ChEMBL MCP Server

get_dose_response

Retrieve dose-response data and activity profiles for chemical compounds from ChEMBL database to analyze biological effects and potency.

Instructions

Get dose-response data and activity profiles for compounds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
molecule_chembl_idYesChEMBL compound ID
target_chembl_idNoChEMBL target ID (optional filter)

Implementation Reference

  • The main handler function for the 'get_dose_response' tool. It validates input arguments, queries the ChEMBL API for activity data filtered by molecule_chembl_id (and optionally target_chembl_id), processes the response to extract dose-response relevant fields (activity_type, value, units, etc.), and returns formatted JSON output.
    private async handleGetDoseResponse(args: any) {
      if (!args || typeof args.molecule_chembl_id !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid dose response arguments');
      }
    
      try {
        const params: any = {
          molecule_chembl_id: args.molecule_chembl_id,
          limit: 100,
        };
    
        if (args.target_chembl_id) {
          params.target_chembl_id = args.target_chembl_id;
        }
    
        const response = await this.apiClient.get('/activity.json', { params });
        const activities = response.data.activities || [];
    
        // Group activities by assay and extract dose-response data
        const doseResponseData = activities
          .filter((a: any) => a.standard_value !== null && a.standard_type)
          .map((a: any) => ({
            assay_chembl_id: a.assay_chembl_id,
            target_chembl_id: a.target_chembl_id,
            activity_type: a.standard_type,
            value: a.standard_value,
            units: a.standard_units,
            relation: a.standard_relation,
          }));
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                molecule_chembl_id: args.molecule_chembl_id,
                total_measurements: doseResponseData.length,
                dose_response_data: doseResponseData,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get dose response: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Input schema defining the parameters for the get_dose_response tool: requires molecule_chembl_id (string), optional target_chembl_id (string).
    inputSchema: {
      type: 'object',
      properties: {
        molecule_chembl_id: { type: 'string', description: 'ChEMBL compound ID' },
        target_chembl_id: { type: 'string', description: 'ChEMBL target ID (optional filter)' },
      },
      required: ['molecule_chembl_id'],
    },
  • src/index.ts:561-573 (registration)
    Registration of the get_dose_response tool in the ListToolsRequestSchema response, providing the tool name, description, and input schema to MCP clients.
    {
      name: 'get_dose_response',
      description: 'Get dose-response data and activity profiles for compounds',
      inputSchema: {
        type: 'object',
        properties: {
          molecule_chembl_id: { type: 'string', description: 'ChEMBL compound ID' },
          target_chembl_id: { type: 'string', description: 'ChEMBL target ID (optional filter)' },
        },
        required: ['molecule_chembl_id'],
      },
    },
    {
  • src/index.ts:773-774 (registration)
    Registration/dispatch of the get_dose_response tool handler in the CallToolRequestSchema switch statement.
    case 'get_dose_response':
      return await this.handleGetDoseResponse(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 doesn't specify if this is a read-only operation, requires authentication, has rate limits, or what the output format might be. For a tool with no annotations, 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 any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'dose-response data and activity profiles' entail, how results are returned, or any behavioral traits. For a tool with no structured support, the description should do more to compensate, but it remains minimal.

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 input schema has 100% description coverage, clearly documenting both parameters (molecule_chembl_id and target_chembl_id). The description doesn't add any extra meaning beyond the schema, such as example values or usage tips, so it meets the baseline for adequate but unenhanced parameter semantics.

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 with a specific verb ('Get') and resources ('dose-response data and activity profiles for compounds'), making it understandable. However, it doesn't differentiate from siblings like 'search_activities' or 'compare_activities', which might offer overlapping functionality, so it doesn't reach 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. With many sibling tools like 'search_activities' or 'get_assay_info', there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on the name alone.

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/ChEMBL-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server