Skip to main content
Glama

Common Disease Target Profile

get_common_disease_targets
Read-onlyIdempotent

Profiles top Open Targets drug targets for every disease in a category, such as oncology or metabolic, in parallel. Use it for a fast landscape scan across a whole disease area.

Instructions

Profile the top drug targets for a curated set of common diseases in one call.

Use this for a fast landscape scan across a whole disease area: given a category (e.g. 'oncology'), it looks up the curated MONDO diseases in that category and returns each one's top Open Targets evidence-scored targets, in parallel. To profile a single disease you already have a MONDO ID for, use get_disease_targets instead — this tool is its category-level, multi-disease counterpart and does not accept a raw MONDO ID.

Queries Open Targets live. Returns a JSON string with the category and a profile object mapping each disease to its MONDO ID and top targets. A lookup that fails is reported inline as that disease's error, not raised. status summarises the lookups: success when every one answered, partial when some failed, error when all failed and no targets were retrieved. diseases_requested, diseases_profiled (lookups that succeeded) and diseases_failed give the counts. A failed lookup is not evidence that a disease has no associated targets. Returns a JSON error object listing the valid values when the category — or a disease_name filter within it — is not recognised.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "get_common_disease_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.8

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already supply readOnlyHint, openWorldHint and idempotentHint, and the description adds substantial behavior beyond them: queries Open Targets live, failed lookups are reported inline as per-disease errors rather than raised, and status semantics (success/partial/error) with requested/profiled/failed counts are defined. It also warns that a failed lookup is not evidence of no targets, which is exactly the reasoning trap an agent would fall into. It stops short of stating rate limits, latency, or how many diseases a category typically contains, so it is not a full 5.

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 short paragraphs, front-loaded with purpose, then routing guidance, then return semantics; nearly every sentence carries decision-relevant information. The return-format paragraph partially duplicates what the output schema already declares, which is the main avoidable weight.

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?

By the end an agent knows what the tool does, when to prefer it over get_disease_targets, what category values look like, the partial-failure semantics, and how to interpret an empty or failed disease entry. Nothing needed to invoke it correctly or read its result is missing.

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 reported as 0% at the top level, so the description must carry meaning; it does explain that category is a curated grouping (with an 'oncology' example) and that disease_name is a filter within that category, plus that unrecognised category or disease_name values return a JSON error listing valid values. The target_limit parameter is left entirely to the schema, which keeps it below a 5.

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 ('Profile the top drug targets for a curated set of common diseases in one call') and immediately contrasts itself with the sibling get_disease_targets, so an agent can distinguish category-level from single-disease profiling 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('fast landscape scan across a whole disease area'), names the alternative tool and the condition that selects it (a single disease you already have a MONDO ID for), and states the exclusion that this tool does not accept a raw MONDO ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.