fda_link_subsidiaries
ActiveTool of FDA Data MCP
declared in 0.1.0
Explicitly link existing company records under a parent company for family-level rollups. Use this when names like Actavis or Cephalon already belong to their own company_id and should roll up under a parent like Teva. This preserves alias collision safety while making manufacturing and facility summaries family-aware.
Parameters schema
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"parent_company",
"subsidiaries"
],
"properties": {
"subsidiaries": {
"type": "array",
"items": {
"type": "object",
"required": [
"company"
],
"properties": {
"notes": {
"type": "string",
"maxLength": 2000,
"description": "Optional notes about the relationship"
},
"source": {
"type": "string",
"maxLength": 500,
"description": "Relationship source identifier"
},
"company": {
"type": "string",
"maxLength": 500,
"description": "Existing company name to link under the parent"
},
"confidence": {
"type": "number",
"maximum": 1,
"minimum": 0,
"description": "Relationship confidence between 0 and 1"
}
}
},
"maxItems": 100,
"minItems": 1,
"description": "Subsidiary company records to link"
},
"parent_company": {
"type": "string",
"maxLength": 500,
"description": "Parent company that should own the family rollup"
}
}
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
FDA Data MCP
https://github.com/medley/fda-data
1/7 registries