Skip to main content
Glama

Molecule

molecule
Read-onlyIdempotent

Full molecule record by ChEMBL ID (e.g. "CHEMBL25" = aspirin).

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": {
      "chembl_id": "CHEMBL25"
    },
    "name": "molecule"
  }
}

Input Schema

NameRequiredDescriptionDefault
chembl_idYes

Output Schema

NameRequiredDescriptionDefault
max_phaseNoMaximum development phase
pref_nameNoPreferred name
molecule_typeNoType of molecule
structure_typeNo
cross_referencesNo
therapeutic_flagsNo
molecule_chembl_idNoChEMBL molecule ID
molecule_propertiesNo
molecule_structuresNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / max_phase / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "number",
      +  "null",
      +  "string"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety and repeatability are covered. The description adds only the notion of a 'full' record, with no mention of error behavior for unknown IDs or what completeness means in practice.

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?

One compact sentence with the resource front-loaded and the example parenthetically attached where it helps most. Nothing is wasted, though the wording is so terse that the action verb is only implied.

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?

An output schema and rich annotations mean the description needn't explain returns or safety, and the lone parameter is well illustrated. Gaps remain in routing guidance versus search siblings and in what happens on an invalid or missing identifier.

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 0%, so the description carries the burden for the single parameter, and it does: it names the identifier system (ChEMBL ID) and supplies a concrete example ('CHEMBL25' = aspirin) that anchors both format and meaning. It leaves out validation rules such as case sensitivity or prefix handling.

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 names the specific resource ('Full molecule record') and the lookup key ('by ChEMBL ID'), which is enough to separate it from lookups that return partial or aggregated data. It stops short of explicitly contrasting with chembl_search or chembl_target, so the agent must still infer that those are the discovery-oriented siblings.

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?

The phrase 'by ChEMBL ID' implicitly tells the agent that a known identifier is a precondition, and the aspirin example clarifies the input shape. However, there is no explicit statement of when to prefer this over search-style siblings or what to do when the ID is unknown.

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.