BMI & Fitness Metrics SkillBMI & Fitness Metrics Skill

OnlineCredit Usage:1 per callTool:BMIFitnessMetricsSkill

The tool

Give your agent body metrics. Call it as an MCP tool to compute BMI, BMR, TDEE, calorie targets and macros from height, weight and age.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as BMIFitnessMetricsSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "BMIFitnessMetricsSkill",
  "arguments": {
    "weight": "180",
    "height": "70",
    "unit": "imperial"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about 180 in the terms this source covers is enough for it to reach for BMIFitnessMetricsSkill on its own.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
weightRequirednumber180Weight in kg (metric) or lbs (imperial)
heightRequirednumber70Height in cm (metric) or inches (imperial)
unitRequiredstringimperialUnit system for weight and height One of: metric, imperial.
agenumber30Age in years (required for BMR/TDEE calculations)
genderstringmaleGender (required for BMR/TDEE calculations) One of: male, female.
activityLevelstringmoderateActivity level (required for TDEE/calorie calculations) One of: sedentary, light, moderate, active, veryactive.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "height": "170 cm",
    "weight": "70 kg",
    "bmi": 24.221453287197235,
    "risk": "Low risk",
    "summary": "This weight is normal and you are healthy.",
    "recommendation": "A BMI between 18.5 and 24.9 falls within the 'normal' weight range according to the World Health Organization. This range is associated with the lowest health risk for conditions such as heart disease, diabetes, and certain cancers. However, it's important to note that BMI is not a perfect measure as it does not account for muscle mass, bone density, overall body composition, and racial and sex differences. Therefore, while it's a useful starting point, it should not be the only measure of one's health."
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
heightstring170 cmFormatted height with unit
weightstring70 kgFormatted weight with unit
bminumber24.221453287197235Calculated Body Mass Index
riskPremiumstringLow riskHealth risk level based on BMI category
summaryPremiumstringThis weight is normal and you are healthy.Brief interpretation of BMI results
recommendationstringA BMI between 18.5 and 24.9 falls within the 'normal' weight range according to the World Health Organization. This range is associated with the lowest health risk for conditions such as heart disease, diabetes, and certain cancers. However, it's important to note that BMI is not a perfect measure as it does not account for muscle mass, bone density, overall body composition, and racial and sex differences. Therefore, while it's a useful starting point, it should not be the only measure of one's health.

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use BMI & Fitness Metrics Skill

Set up BMI & Fitness Metrics Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use BMIFitnessMetricsSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?