Médicaments en France

Get availability

get_availability

Read-onlyIdempotent

Current ANSM shortage status of one medicine, given exactly one of: its CIS code, an ANSM shortage id or a name. Returns the status, the expected return in ANSM's wording, the change history and possibly related unlinked entries. Information only: never use this to recommend a substitute, an alternative or an equivalent medicine, a dosage change or stopping a treatment. Other medicines in the results are not alternatives.

Input Schema

Name	Required	Description
`cis`	No	8-digit BDPM medicine code (CIS).
`name`	No	Medicine name; resolved to one CIS or a list of candidates.
`shortage_id`	No	ANSM shortage id: the numeric id of an ANSM shortage entry.

Output Schema

Name	Required	Description	Default
`data`	Yes
`safety`	Yes
`source`	Yes
`warning`	No
`disclaimer`	Yes
`coverage_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / shortage_id / description

Previous value: -"ANSM shortage id, as returned by the other tools."New value: +"ANSM shortage id: the numeric id of an ANSM shortage entry."

Changed2 schema fields changedOct 28, 2026

addedOutput schema / properties / source / properties / bdpm_imported_at

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / source / required

Previous value: -[
-  "ansm",
-  "bdpm",
-  "ansm_last_ingest",
-  "bdpm_release"
-]New value: +[
+  "ansm",
+  "bdpm",
+  "ansm_last_ingest",
+  "bdpm_release",
+  "bdpm_imported_at"
+]

First observedOct 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish that this is a safe, read-only, idempotent operation, and the description adds useful behavioral context beyond that. It discloses what is returned (status, expected return in ANSM's wording, change history, possibly related unlinked entries) and includes an explicit safety boundary against using the result for clinical recommendations. It does not contradict any annotation.

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 front-loaded with the core purpose and input constraint, then covers return contents and safety restrictions in compact sentences. The final note that other medicines in results are not alternatives reinforces the safety boundary without excessive repetition.

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

Completeness5/5

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

Given rich annotations, an output schema, full schema description coverage, and three optional identifier parameters, the description supplies everything an agent needs to call the tool correctly. It covers purpose, identifier selection, return behavior, and the key safety limitation.

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 coverage is 100%, so parameter meanings are already documented in the schema. The description still adds an important semantic constraint not encoded in the schema: exactly one of cis, shortage_id, or name must be supplied. That is meaningful beyond the structured parameter descriptions.

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: getting the current ANSM shortage status of one medicine. It also distinguishes the scope from list-oriented siblings by specifying exactly one medicine and exactly one identifier. An agent can identify the intended operation without opening another schema.

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?

The description gives clear usage conditions: exactly one of CIS code, ANSM shortage id, or name, and it explicitly says the tool is information-only and must not be used to recommend substitutes, alternatives, dosage changes, or stopping treatment. It does not explicitly route the agent among siblings such as search_medicine or list_current_shortages, so it falls short of the strongest usage-guidance score.

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

All Médicaments en France 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.