Skip to main content
Glama

Search Targets

search_targets
Read-onlyIdempotent

Search the Guide to PHARMACOLOGY (IUPHAR/BPS), an expert-curated pharmacology database, for protein targets by name. Returns matching targets with their GtoPdb target id, abbreviation, and type (e.g. GPCR, CatalyticReceptor, Enzyme, Transporter). Use the returned target id with target_interactions to find ligands that bind it. Requires a GtoPdb API key, register free at guidetopharmacology.org/login.jsp and pass your own via _apiKey. Complements ChEMBL/DrugBank.

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": {
      "name": "EGFR",
      "_apiKey": "your-guidetopharmacology-api-key"
    },
    "name": "search_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTarget name or fragment to search for, e.g. "EGFR" or "dopamine receptor".
limitNoMax results to return (default 15).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "name": "EGFR"
      -  },
      -  {
      -    "limit": 20,
      -    "name": "dopamine receptor"
      -  }
      -]New value: +[
      +  {
      +    "_apiKey": "your-guidetopharmacology-api-key",
      +    "name": "EGFR"
      +  },
      +  {
      +    "_apiKey": "your-guidetopharmacology-api-key",
      +    "limit": 20,
      +    "name": "dopamine receptor"
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "name": "EGFR"
      +  },
      +  {
      +    "limit": 20,
      +    "name": "dopamine receptor"
      +  }
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's value is in what they don't say: the tool requires a user-supplied GtoPdb API key with a registration URL, and the response shape is enumerated. It omits pagination behavior and whether name matching is fuzzy or exact, 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?

Four sentences, each doing distinct work: purpose, return fields, downstream chaining, auth prerequisite. Front-loaded with the core action and no redundant restatement of the title.

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

Completeness5/5

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

For a two-parameter read-only lookup with no output schema, the description supplies everything an agent needs: what to search, what is returned, how to use the result, and the auth gate. Nothing material is missing.

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% for the two declared parameters, so the baseline is 3. The description does add meaning for _apiKey (self-registration and how to pass it), which the schema never declares, but it says nothing extra about limit behavior, so the net gain over the schema is modest.

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 (search) and resource (protein targets in the Guide to PHARMACOLOGY by name), plus exactly what comes back (GtoPdb target id, abbreviation, and type with concrete type examples). This cleanly separates it from ligands-oriented siblings such as search_ligands and target_interactions.

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?

Gives an explicit downstream recipe: take the returned target id into target_interactions to find binding ligands, and notes it complements ChEMBL/DrugBank. It stops short of stating when this database should not be used or naming in-catalog alternatives, so it is clear context rather than full when/when-not guidance.

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.