Skip to main content
Glama

Activities

activities
Read-onlyIdempotent

Retrieve bioactivity records from ChEMBL filtered by molecule_chembl_id and/or target_chembl_id; returns IC50/Ki/EC50 values, assay descriptions, and units. This is SMALL-MOLECULE assay data: a biologic such as an antibody has none by construction, and the response says so rather than returning a bare empty list.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "molecule_chembl_id": "CHEMBL25"
    },
    "name": "activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-1000 (default 25).
target_chembl_idNo
molecule_chembl_idNo

Output Schema

NameRequiredDescriptionDefault
page_metaNo
activitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / page_meta / properties / next / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • changedOutput schema / properties / activities / items / properties / data_validity_comment / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / activities / items / properties / data_validity_description / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / activities / items / properties / molecule_pref_name / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "string"
      +]
  3. Changed4 schema fields changed
    • changedOutput schema / properties / activities / items / properties / qudt_units / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / activities / items / properties / standard_units / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / activities / items / properties / units / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / activities / items / properties / uo_units / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds useful behavioral context: it names the returned measurement types (IC50/Ki/EC50), mentions assay descriptions and units, and explicitly says the response reports the biologic/no-activity case rather than returning a bare empty list.

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?

Two sentences, front-loaded with the core action and filters, then followed by the important edge-case note. There is no filler and every clause contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so the description need not explain return structure exhaustively, and the annotations already cover safety. The description still adds the key bioactivity return context and the biologic edge case, though it does not clarify pagination or the meaning of the limit parameter beyond what the schema provides.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, but the description compensates by explaining that molecule_chembl_id and target_chembl_id are filters and can be used together ('and/or'). It does not add format details for those IDs, and the limit parameter is only documented in the schema, but the key filtering semantics are well covered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Retrieve), specific resource (bioactivity records from ChEMBL), and specific filters (molecule_chembl_id and/or target_chembl_id), plus the returned data types. It also distinguishes its scope from other ChEMBL tools by emphasizing small-molecule assay data and the biologic edge case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains that the tool filters by molecule and/or target and notes the small-molecule caveat, which implies appropriate usage. However, it gives no explicit when-to-use guidance versus sibling tools such as chembl_mechanism or chembl_target, and it does not state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.