Diplomètre

Lire les chiffres d’une formation

lire_formation

Read-onlyIdempotent

Combien ça coûte ? Est-ce que ça mène à un emploi ? Le diplôme est-il reconnu ? Consultez la fiche d’une formation dans Diplomètre : accès, réussite, poursuite d’études, emploi, salaire, frais et reconnaissance du diplôme. Les chiffres officiels et sourcés sont accompagnés des autres données disponibles, dont la fiabilité reste indiquée. Chaque chiffre donne son producteur et son année, ou « non communiqué » s’il manque. Le taux d’accès ne prédit pas votre admission. La réponse inclut le lien vers la fiche.

Input Schema

Name	Required	Description	Default
`identifiant`	Yes	Identifiant public de la formation (fin de l’adresse de sa page Diplomètre, en lettres minuscules, chiffres et tirets) ou adresse complète de cette page

Output Schema

Name	Required	Description	Default
`rappels`	No
`formations`	Yes
`introuvables`	No
`avertissements`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / properties / formations / items / properties / chiffres / items / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "etat": {
-        "const": "disponible",
-        "type": "string"
-      },
-      "indicateur": {
-        "type": "string"
-      },
-      "notes": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "precision": {
-        "type": "string"
-      },
-      "question": {
-        "type": "string"
-      },
-      "source": {
-        "anyOf": [
-          {
-            "additionalProperties": false,
-            "properties": {
-              "annee": {
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "fiabilite": {
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "licence": {
-                "type": "string"
-              },
-              "producteur": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "producteur",
-              "annee",
-              "fiabilite"
-            ],
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "unite": {
-        "type": "string"
-      },
-      "valeur": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "indicateur",
-      "question",
-      "etat",
-      "valeur",
-      "source"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "etat": {
-        "const": "non communiqué",
-        "type": "string"
-      },
-      "indicateur": {
-        "type": "string"
-      },
-      "motif": {
-        "type": "string"
-      },
-      "question": {
-        "type": "string"
-      },
-      "source": {
-        "type": "null"
-      },
-      "valeur": {
-        "type": "null"
-      }
-    },
-    "required": [
-      "indicateur",
-      "question",
-      "etat",
-      "valeur",
-      "source"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "etat": {
+        "const": "disponible",
+        "type": "string"
+      },
+      "indicateur": {
+        "type": "string"
+      },
+      "notes": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "precision": {
+        "type": "string"
+      },
+      "question": {
+        "type": "string"
+      },
+      "source": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "annee": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "fiabilite": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "licence": {
+                "type": "string"
+              },
+              "producteur": {
+                "type": "string"
+              },
+              "reference": {
+                "type": "string"
+              },
+              "validite": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "producteur",
+              "annee",
+              "fiabilite"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "unite": {
+        "type": "string"
+      },
+      "valeur": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "indicateur",
+      "question",
+      "etat",
+      "valeur",
+      "source"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "etat": {
+        "const": "non communiqué",
+        "type": "string"
+      },
+      "indicateur": {
+        "type": "string"
+      },
+      "motif": {
+        "type": "string"
+      },
+      "question": {
+        "type": "string"
+      },
+      "source": {
+        "type": "null"
+      },
+      "valeur": {
+        "type": "null"
+      }
+    },
+    "required": [
+      "indicateur",
+      "question",
+      "etat",
+      "valeur",
+      "source"
+    ],
+    "type": "object"
+  }
+]

First observedOct 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: each figure carries its producer and year or 'non communiqué', reliability is flagged, and it warns that 'le taux d'accès ne prédit pas votre admission' – a caveat that prevents an agent from misinterpreting the metric. Provenance and data-quality semantics are spelled out.

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 three opening questions act as an intent-matching hook rather than pure filler, and the core purpose statement backed by the field list is dense with information. It is slightly back-loaded – the actual 'consultez la fiche' purpose arrives after the questions – but no sentence is truly wasted.

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 an output schema present, return structure needn't be explained, and annotations cover safety. The description still completes the picture by describing data provenance, reliability caveats, and the metric-interpretation warning, leaving little an agent would need that isn't already in the structured fields.

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?

There is only one parameter and schema description coverage is 100%, so the schema already fully documents 'identifiant' including its lowercase/dash format and full-URL alternative. The description adds nothing about the parameter, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Consultez la fiche d'une formation') and enumerates the exact fields returned – accès, réussite, poursuite d'études, emploi, salaire, frais, reconnaissance du diplôme – so an agent knows precisely what this tool yields. It is clearly distinguishable from sibling tools like rechercher_formations or comparer_formations by its single-formation 'fiche' scope, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied, via the framing questions (cost, employment outcomes, diploma recognition), which suggest the situations that call for this data. There is no explicit when-to-use statement, no exclusion, and no pointer to the alternative tools for searching or comparing formations.

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

All Diplomètre 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.

Resources

Need Help?