Skip to main content
Glama

China Licensing Deals

china_licensing_deals
Read-onlyIdempotent

Biotech and pharmaceutical licensing deals involving China, a Chinese company out-licensing a drug to a Western partner, or a Western company licensing rights INTO Greater China. Returns the two companies, the drug or asset, the territory, the upfront payment, milestone totals and royalty terms, with the SEC filing they were announced in and its date. Answers "which Chinese biotechs signed out-licensing deals", "recent China pharma licensing deals", "who licensed rights in Greater China". Sourced from SEC 8-K announcements, so it covers any deal with a US-listed party. Filter by company, drug name or date window.

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": {
      "limit": 10,
      "since": "2026-06-01"
    },
    "name": "china_licensing_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum deals to return, 1-40 (default 10).
queryNoOptional extra term to narrow the search, a company ("Hengrui"), a drug ("VIZZ"), a modality ("ADC", "bispecific") or a therapy area ("oncology"). Combined with the deal and China terms, not replacing them.
sinceNoEarliest filing date (YYYY-MM-DD). Defaults to 90 days ago.
untilNoLatest filing date (YYYY-MM-DD). Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Optional extra term to narrow the search — a company (\"Hengrui\"), a drug (\"VIZZ\"), a modality (\"ADC\", \"bispecific\") or a therapy area (\"oncology\"). Combined with the deal and China terms, not replacing them."New value: +"Optional extra term to narrow the search, a company (\"Hengrui\"), a drug (\"VIZZ\"), a modality (\"ADC\", \"bispecific\") or a therapy area (\"oncology\"). Combined with the deal and China terms, not replacing them."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's real contribution is the coverage boundary: results come from SEC 8-K filings and therefore only include deals with a US-listed party. That is a material limitation an agent could not infer from structured fields, though pagination/result caps are left to the schema.

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?

The opening sentence front-loads the scope and the coverage is dense rather than padded. The quoted example questions partially duplicate what the preceding clauses already established, so a small amount of text does not earn its place.

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?

With no output schema, the description usefully enumerates return fields (companies, asset, territory, upfront, milestones, royalties, filing and date) and discloses the SEC-based coverage limit. Only result-cap/pagination behavior is left implicit in the schema, so the definition is nearly complete for a four-parameter read tool.

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%, so all four parameters are already documented in the schema, including the query term's role and the date defaults. The description only restates this at a high level ('filter by company, drug name or date window') and adds no syntax or behavioral detail beyond 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?

The description states a specific verb-and-resource combination (retrieving biotech/pharma licensing deals involving China) and immediately disambiguates both directions: Chinese out-licensing to a Western partner and Western in-licensing into Greater China. It then enumerates the returned fields and the data source, so an agent knows exactly what this tool produces.

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?

Concrete usage is given through three example questions ('which Chinese biotechs signed out-licensing deals', 'recent China pharma licensing deals', 'who licensed rights in Greater China') plus a filtering hint. It does not name a sibling alternative or state when NOT to use it, so it stops short of full routing 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.