Skip to main content
Glama

Target Interactions

target_interactions
Read-onlyIdempotent

List the quantitative ligand interactions for a protein target in the Guide to PHARMACOLOGY (IUPHAR/BPS). Given a GtoPdb target id (from search_targets), returns the ligands acting on it with interaction type (Agonist/Antagonist/Inhibitor/etc.), action, and binding affinity (e.g. pKi/pIC50). Requires a GtoPdb API key, register free at guidetopharmacology.org/login.jsp and pass your own via _apiKey.

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": {
      "_apiKey": "your-guidetopharmacology-api-key",
      "target_id": 1797
    },
    "name": "target_interactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax interactions to return (default 25).
target_idYesGtoPdb target id, e.g. 1797 for EGFR.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered; the description adds the genuinely useful behavior: an external API key must be supplied per call and where to obtain it. It also previews the payload shape (interaction type, action, affinity values), though it does not discuss pagination or behavior when a target has many interactions.

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?

Three sentences, front-loaded with purpose, then return contents, then the auth caveat – no filler. The API-key registration clause is a bit long but is required operational information rather than padding.

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?

With only two parameters, no nested objects, and no output schema, the description carries everything needed: what is queried, what comes back, how to get the id, and how to authenticate. An agent could call this correctly on the first attempt.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: target_id is a GtoPdb id sourced from search_targets, and _apiKey is a personal key passed on the call – notable because _apiKey appears only in examples, not in the schema properties. Limit behavior (max interactions) and defaults are left largely to the schema.

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?

"List the quantitative ligand interactions for a protein target" gives a specific verb and resource, names the source database (Guide to PHARMACOLOGY / IUPHAR-BPS), and anchors the direction of the lookup (target -> ligands), which separates it from a ligand-first sibling. It also names the sibling that produces the required id, so the agent can place it in a workflow.

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?

It states the prerequisite for use (a GtoPdb target id obtained from search_targets) and the auth requirement with a concrete registration path. What is missing is an explicit exclusion – e.g. when to prefer a ligand-centric lookup – but the target-first framing makes the intended case clear.

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.