Elfy.Life

Calculer l'indice QUICKI

calculate_quicki

Read-onlyIdempotent

Calcule l'indice QUICKI (sensibilité à l'insuline) à partir de la glycémie à jeun (mmol/l, ou mg/dl avec glycemiaUnit) et de l'insulinémie à jeun (mUI/l), avec l'interprétation et les seuils publiés sur Elfy.Life. Le résultat est accompagné d'un avertissement : ce n'est pas un diagnostic médical.

Input Schema

Name	Required	Description	Default
`glycemiaUnit`	No	unité de la glycémie : mmol/l (défaut) ou mg/dl	mmol/l
`glycemiaMmolL`	Yes	glycémie à jeun, dans l'unité glycemiaUnit (mmol/l par défaut, malgré le nom)
`insulinemiaMicroUiMl`	Yes	insulinémie à jeun, en mUI/l (équivalent µUI/ml)

Output Schema

Name	Required	Description
`index`	Yes
`value`	Yes
`inputs`	Yes
`disclaimer`	Yes
`thresholds`	Yes	plages d'interprétation publiées (bornes null = non bornées)
`calculatorUrl`	Yes
`interpretation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 30, 2026

changedInput schema / properties / glycemiaMmolL / description

Previous value: -"glycémie à jeun, en mmol/l"New value: +"glycémie à jeun, dans l'unité glycemiaUnit (mmol/l par défaut, malgré le nom)"

addedInput schema / properties / glycemiaUnit

Added value: +{
+  "default": "mmol/l",
+  "description": "unité de la glycémie : mmol/l (défaut) ou mg/dl",
+  "enum": [
+    "mmol/l",
+    "mg/dl"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calculatorUrl": {
+      "format": "uri",
+      "type": "string"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "index": {
+      "enum": [
+        "HOMA",
+        "QUICKI"
+      ],
+      "type": "string"
+    },
+    "inputs": {
+      "properties": {
+        "glycemiaConvertedFrom": {
+          "properties": {
+            "unit": {
+              "enum": [
+                "mg/dl"
+              ],
+              "type": "string"
+            },
+            "value": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "value",
+            "unit"
+          ],
+          "type": "object"
+        },
+        "glycemiaMmolL": {
+          "type": "number"
+        },
+        "insulinemiaMicroUiMl": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "glycemiaMmolL",
+        "insulinemiaMicroUiMl"
+      ],
+      "type": "object"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "thresholds": {
+      "description": "plages d'interprétation publiées (bornes null = non bornées)",
+      "items": {
+        "properties": {
+          "interpretation": {
+            "type": "string"
+          },
+          "max": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "maxInclusive": {
+            "type": "boolean"
+          },
+          "min": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "minInclusive": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "min",
+          "minInclusive",
+          "max",
+          "maxInclusive",
+          "interpretation"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "value": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "index",
+    "value",
+    "interpretation",
+    "thresholds",
+    "inputs",
+    "disclaimer",
+    "calculatorUrl"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare the safe, read-only, idempotent profile, so the bar is lower; the description still adds real value by disclosing that the result comes bundled with published interpretation thresholds from Elfy.Life and a non-diagnostic disclaimer. It stops short of describing output structure, but that is covered by the output schema.

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?

Two tightly packed sentences that front-load the computation and its inputs, then the ancillary warning. Nothing is redundant, though the parenthetical unit enumeration slightly duplicates schema text.

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 the description needn't explain return values, and it does cover inputs, interpretation, and the medical disclaimer. What's missing is any guidance on sibling selection or input validity ranges, a small gap for a 3-parameter calculation tool.

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?

Schema description coverage is 100%, so the tripled parameter documentation already carries the semantics and baseline 3 applies. The description only restates the unit handling ('mg/dl avec glycemiaUnit') already spelled out in the schema and adds no conversion formula or range constraints.

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?

States a specific verb and resource ('Calcule l'indice QUICKI') and names the exact inputs (glycémie à jeun, insulinémie à jeun) with units, so the agent knows precisely what the tool computes. It does not, however, explicitly distinguish itself from the sibling calculate_homa, which computes a related insulin-sensitivity index.

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?

The description implies its use case (deriving a QUICKI insulin-sensitivity score from fasting labs) but never states when to pick it over calculate_homa or what preconditions apply. The rubric's 3 ('implied usage') fits: an agent can infer intent but gets no explicit routing guidance.

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

All Elfy.Life 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?