Skip to main content
Glama

Chembl Search

chembl_search
Read-onlyIdempotent

Full-text search the ChEMBL drug-discovery database for molecules, targets, assays, or documents; returns ChEMBL IDs and summary fields you can pass to molecule, target, or activities. Pair with chembl_mechanism, which takes a drug name directly and returns its mechanism of action and target.

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": {
      "query": "aspirin"
    },
    "name": "chembl_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNomolecule (default) | target | assay | document
limitNo1-1000 (default 25).
queryYesFree-text query.

Output Schema

NameRequiredDescriptionDefault
assaysNoAssay search results
targetsNoTarget search results
documentsNoDocument search results
moleculesNoMolecule search results
page_metaNoPagination metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the return shape (ChEMBL IDs plus summary fields) and the intended chaining pattern into follow-up tools. It does not mention result caps, ranking, or rate limits, which keeps it from a 5.

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 verb and data source, then the return value, then sibling routing. No filler, no restatement of the title, and the semicolon keeps the return contract attached to the search action.

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?

An output schema exists, so return values need not be detailed, and the description nonetheless sketches what comes back and how to use it downstream. For a three-parameter read-only search that is nearly complete; only edge behaviors like pagination or result caps are unaddressed.

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 type, limit and query are already documented in structured fields, and this is the baseline case. The description restates the four entity types in prose but adds no enum constraints, defaults, or syntax guidance beyond what the schema provides.

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 ('Full-text search the ChEMBL drug-discovery database') plus the exact entity types covered (molecules, targets, assays, documents) and what comes back (ChEMBL IDs and summary fields). It also names a sibling, chembl_mechanism, and contrasts its input shape (drug name directly), so an agent can discriminate without opening either 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?

Provides clear downstream routing: results can be passed to `molecule`, `target`, or `activities`, and it explains when chembl_mechanism is the better pick (it takes a drug name directly). It stops short of an explicit exclusion such as 'use this only for discovery, not for mechanism lookup', but the implied split is strong.

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.