Prognyx oncology intelligence

Compare trials around an asset

compare_trials

Read-only

Up to three interventional ClinicalTrials.gov studies matching an asset or target AND an oncology indication, side by side: sponsor, phase, status, declared arms, primary outcomes, last update, registry URL. Active studies first, then later phase; different sponsors where possible. Use a target (e.g. "KIF18A", "B7-H3") rather than one drug name to see other programmes.

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": {
      "asset": "<asset>",
      "indication": "<indication>"
    },
    "name": "compare_trials"
  }
}

Input Schema

Name	Required	Description	Default
`asset`	Yes	Public asset or target, e.g. "sotorasib", "KRAS G12C", "B7-H3".
`indication`	Yes	Oncology indication, e.g. "colorectal cancer", "NSCLC".

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety behavior is covered. The description adds valuable context beyond annotations: it limits results to up to three interventional studies, lists returned fields, and discloses ordering and selection heuristics. It still omits edge cases such as fewer than three matches or error behavior.

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?

The description is three purposeful sentences with no filler. It front-loads the comparison constraint and result cap, then lists returned fields, then gives a targeted usage hint. Every sentence adds either scope or selection guidance.

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

Completeness4/5

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

Given the two required parameters, 100% schema coverage, annotations covering the read-only/open-world profile, and no output schema, the description is nearly complete. It lists the returned fields and selection order, which compensates for the absent output schema. Minor gaps remain around empty results or when fewer than three studies match.

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 100%, so the parameters are already documented with examples. The description still adds meaning by clarifying that asset may be a target rather than a drug name, and recommends using a target to reveal other programmes. That is useful guidance beyond the schema.

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 states a specific verb and resource: comparing up to three interventional ClinicalTrials.gov studies for an asset/target and oncology indication. It also names the exact fields presented side by side, making the tool's output concrete. It does not distinguish itself from sibling tools such as search_briefings or search_registry, so it falls short of a 5.

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 description implies the tool is for side-by-side trial comparison when an asset/target and oncology indication are known. It offers a useful parameter-level guideline: use a target rather than one drug name to see other programmes. However, it does not explicitly state when to use this tool versus the sibling search tools, nor does it state exclusions.

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

All Prognyx oncology intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?