Skip to main content
Glama
Sign In
macalc

macalc

by tresor4k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

calculate_bmi

Read-onlyIdempotent

Calculate Body Mass Index and determine WHO weight category from weight and height. Use this screening tool for adult BMI assessment.

Instructions

Calculate Body Mass Index and the corresponding WHO weight category for an adult. Inputs: weight_kg (kilograms) and height_cm (centimeters). Returns the BMI value and category. Read-only and deterministic. Screening indicator only — not a medical diagnosis; not valid for children or athletes with high muscle mass.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "weight_kg": "<weight_kg>",
      "height_cm": "<height_cm>"
    },
    "name": "calculate_bmi"
  }
}

Input Schema

NameRequiredDescriptionDefault
height_cmYesHeight in centimeters
weight_kgYesWeight in kilograms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "formula": {
-      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
-      "type": "string"
-    },
-    "reference_url": {
-      "description": "Link to a calcul2 page documenting the calculation in detail.",
-      "type": "string"
-    },
-    "result": {
-      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
-    },
-    "source": {
-      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changedv0.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "formula": {
+      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
+      "type": "string"
+    },
+    "reference_url": {
+      "description": "Link to a calcul2 page documenting the calculation in detail.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
+    },
+    "source": {
+      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Addedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds that it is read-only and deterministic, and discloses return values (BMI and category) and limitations, complementing annotations without contradiction.

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?

Two concise sentences: first states purpose, second lists inputs and outputs, third adds limitations. No unnecessary words, front-loaded with key information.

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?

Despite no output schema, the description states the tool returns BMI value and category, and includes usage restrictions. For a simple tool with two parameters, this is complete and actionable.

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%. The description mentions weight in kilograms and height in centimeters, matching schema units, but adds no additional meaning beyond that. Baseline score of 3 is appropriate.

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 clearly states it calculates BMI and WHO weight category, specifying inputs and outputs. It distinguishes this tool from sibling calculator tools (e.g., tax, interest) by focusing on a specific health metric.

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

Usage Guidelines5/5

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

Explicitly states the tool is a screening indicator only, not a medical diagnosis, and not valid for children or athletes with high muscle mass. This provides clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools