Health
Compute CI = CO / BSA with BSA from the Mosteller formula √(height × weight / 3600). Normal 2.5–4.0 L/min/m². Derived from Mosteller NEJM 1987, Du Bois 1916, StatPearls, LITFL. Not medical advice.
Call this tool from your code in three languages.
curl -X POST 'http://127.0.0.1:3003/en/api/tools/cardiac-index-calculator' \
-H 'Content-Type: application/json' \
-d '{"co":5,"height":175,"weight":75,"decimalPlaces":2}'Send a POST request with your inputs as JSON. File parameters require a separate upload first.
POST http://127.0.0.1:3003/en/api/tools/cardiac-index-calculator| Name | Type | Required | Description |
|---|---|---|---|
| co | number | Yes | Cardiac output in L/min (from thermodilution, Fick, or echo). |
| height | number | Yes | Patient height in centimeters, used to compute BSA via Mosteller. |
| weight | number | Yes | Patient weight in kilograms, used to compute BSA via Mosteller. |
| decimalPlaces | number | No | — |
JSON result
{
"key": {...},
"metadata": {
"key": "value"
},
"error": "Error message (optional)",
"message": "Notification message (optional)"
}Add this tool to your Model Context Protocol server so AI agents can list and call it.
Add this block to your MCP client configuration:
{
"mcpServers": {
"elysiatools-cardiac-index-calculator": {
"name": "cardiac-index-calculator",
"description": "Compute CI = CO / BSA with BSA from the Mosteller formula √(height × weight / 3600). Normal 2.5–4.0 L/min/m². Derived from Mosteller NEJM 1987, Du Bois 1916, StatPearls, LITFL. Not medical advice.",
"baseUrl": "http://127.0.0.1:3003/mcp/sse?toolId=cardiac-index-calculator",
"command": "",
"args": [],
"env": {},
"isActive": true,
"type": "sse"
}
}
}After connecting to the SSE endpoint, list the exposed tools:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}Invoke the tool by its id, passing arguments built from its parameters:
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "cardiac-index-calculator",
"arguments": {
"co": 5,
"height": 175,
"weight": 75,
"decimalPlaces": 2
}
}
}Questions or issues? Contact [email protected]