lsk_… bearer and return content + structuredContent.
Routing at a glance
| If the agent needs… | Tool |
|---|---|
| structured sources for a query | search |
| a concise cited answer | answer |
| an answer accounting for a patient profile | context |
| to apply a rule across patient health records | analyse |
| an antibiotic decision | atb (roadmap — not yet available) |
| a medication datum | drug (roadmap — not yet available) |
search
Structured, citable retrieval — never a free-form answer.| Argument | Type | Notes |
|---|---|---|
query | string | Clinical query (French). |
source_ids | int[] | Optional source allow-list. |
limit | int | Max document units (default 10). |
max_chunks_per_unit | int | Best chunks per unit (default 3). |
answer
Concise answer grounded only in the knowledge base, with citations.| Argument | Type | Notes |
|---|---|---|
query | string | Clinical question (French). |
source_ids | int[] | Optional source allow-list. |
context
Likeanswer, accounting for a coarse patient profile and surfacing conflicts.
| Argument | Type | Notes |
|---|---|---|
query | string | Clinical question (French). |
patient_context | object | { sex, age, history, active_problems, allergies, current_treatments }. |
source_ids | int[] | Optional source allow-list. |
analyse
Apply a free-text clinical rule to inline health records; return matches with KB-grounded recommendations.| Argument | Type | Notes |
|---|---|---|
rule | string | The clinical rule / “équation type”. |
records | object[] | Inline patient health records. |
source_ids | int[] | Optional source allow-list for the recommendation. |
Roadmap tools
atb and drug are not yet registered on the MCP server. Their intended
shape is documented under Roadmap so integrators can plan; they
will appear in tools/list only once shipped.