Skip to main content
Glama

EMBL-EBI ChEMBL molecule search by name or term: ChEMBL ID

health_chEMBL_bioactive_molecules
Read-only

EMBL-EBI ChEMBL molecule search by name or term (q, 2 to 100 characters, e.g. imatinib, aspirin): ChEMBL ID, preferred name, maximum clinical phase, molecule type, molecular weight, canonical SMILES, first approval year and ATC codes, up to 20 molecules per call (max, default 5) with the total match count. Use it to identify a drug or bioactive compound and its development stage; for chemical identifiers and properties by PubChem CID use health_pubchem_chemical_cid, for US approval records health_fda_orange_book. Read-only. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "health_chEMBL_bioactive_molecules"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesMolecule name or term, letters, digits, spaces and hyphens, 2 to 100 characters
maxNoHow many molecules, 1 to 20 (default 5)

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
sourceNo
checkedAtNo
moleculesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantive context beyond them: per-call pricing ($0.002 via x402 on named networks) and that failed calls are not charged. "Read-only" merely restates the annotation, but the payment behavior is information the agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb, resource and key constraints, then alternatives, then pricing — a sensible order with no filler sentences. The long enumeration of return fields is somewhat redundant given an output schema exists.

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?

Covers result caps, total match count, cost model and sibling routing, and an output schema exists so return format need not be spelled out. Nothing critical is missing, though match-count behavior and error conditions are only lightly touched.

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 coverage is 100%, so the schema already documents both parameters and the description largely restates the q length range and max default/cap. It does add concrete example terms (imatinib, aspirin) and ties max to returning the total match count, but this is marginal added meaning.

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?

States a specific verb and resource ("ChEMBL molecule search by name or term") plus the returned fields (ChEMBL ID, preferred name, clinical phase, SMILES, ATC codes) and paging cap. An agent can tell exactly what this returns without opening the schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to alternatives: health_pubchem_chemical_cid for PubChem CID lookups and health_fda_orange_book for US approval records. It gives clear positive usage ("identify a drug or bioactive compound and its development stage") but no explicit when-not or exclusion cases for this tool itself.

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.

Resources