Skip to main content
Glama

Chembl Target

chembl_target
Read-onlyIdempotent

Target record by ChEMBL target ID.

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": "CHEMBL614"
    },
    "name": "chembl_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
chembl_idYes

Output Schema

NameRequiredDescriptionDefault
tax_idNo
organismNo
pref_nameNoPreferred name
target_typeNoType of target
target_chembl_idNoChEMBL target ID
target_componentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no note on whether a missing ID errors or returns empty, no rate-limit or upstream-freshness context for an open-world lookup.

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

Conciseness3/5

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

One short front-loaded clause with no wasted words, so structure is fine. However, the brevity comes at the cost of under-specification rather than efficiency.

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?

An output schema exists, so return values need not be described. Even so, for an open-world lookup tool in a crowded ChEMBL/molecule/mechanism family, the definition is too thin: it does not say what a target record is used for or how it relates to the sibling tools an agent must choose between.

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 single parameter has 0% schema description coverage; only an example value (CHEMBL614) is supplied. The description partially compensates by naming the parameter as a ChEMBL target ID, but adds no format rule or confirmation that it must be a target (not molecule/assay) identifier.

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

Purpose2/5

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

The text "Target record by ChEMBL target ID" essentially restates the tool name and the required key. It does convey the resource (a ChEMBL target) and that lookup is by identifier, but it uses no real verb and gives no differentiation from siblings such as chembl_search, chembl_mechanism, or molecule.

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?

There is no when-to-use guidance at all: no statement about when to pick this over chembl_search (which presumably finds IDs) or chembl_mechanism (which presumably relates targets to mechanisms). The agent must infer usage entirely from the name.

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.