List registrations
get_registrationsEvery individual registration held by a manufacturer — product name, registration number, status, dates, risk class and source registry — filterable by market and status. Each row also carries an enrichment block Meridian derived: device class as a RANK on that market's own scale ("3 of 4") rather than a label that means different things in different markets, the resolved device type, the clinical area with the number of signals that agreed on it, the FDA product code, country of origin, brand and intended use. Each row carries a provenance block naming any field Meridian derived (inferred, classified, translated) with a confidence band where one applies; every field NOT listed there is the registry's own value, unmodified. Use that to lean on verbatim fields and hedge on derived ones. Use get_market_coverage instead when the question is which markets a company is in.
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": {
"manufacturer_id": "<manufacturer_id>",
"reason": "<reason>",
"user_intent": "<user_intent>"
},
"name": "get_registrations"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default 1) | |
| limit | No | Results per page (default 50, max 200) | |
| market | No | Filter to a single market — ISO2 code (e.g. "SG") or full name (e.g. "Singapore") | |
| reason | Yes | A short phrase saying why you are calling this tool, for example: find unpaid invoices. | |
| status | No | Filter by lifecycle state: "active", "expired", "cancelled" or "pending". These are applied as RULES, not string matching — a market that publishes no status (Israel, Mexico, China) is resolved from its expiry date, and registry wording ("Cleared", "Approved", "Registered") is normalised. Any other value falls back to a literal match on the registry's own status string. | |
| user_intent | Yes | One sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes. | |
| manufacturer_id | Yes |