Skip to main content
Glama

Vücut kitle indeksi

vucut_kitle_indeksi_hesapla
Read-onlyIdempotent

Boy ve kilodan vücut kitle indeksini (VKİ/BMI), DSÖ kategorisini ve sağlıklı kilo aralığını hesaplar.

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": {
      "kiloKg": "<kiloKg>",
      "boyCm": "<boyCm>"
    },
    "name": "vucut_kitle_indeksi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
yasNoYaş (18 altında yetişkin sınıfı uygulanmaz). Varsayılan 30.
boyCmYesBoy (cm).
kiloKgYesKilo (kg).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / yas / description
      Previous value: -"Yaş (çocuk ve ergenlerde yetişkin sınıflandırması uygulanmaz). Varsayılan 30."New value: +"Yaş (18 altında yetişkin sınıfı uygulanmaz). Varsayılan 30."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one piece of real behavioral value beyond that — it names the WHO classification standard used for the category output, which matters because BMI cutoffs differ by standard — but it says nothing about how the optional age parameter alters the result, which is the one behavior an agent could get wrong.

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?

A single well-formed sentence that front-loads the input basis (height and weight) and then the outputs, with no filler, repetition, or restatement of the tool name.

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?

For a three-parameter deterministic calculator with a fully described schema and no output schema, the description is nearly sufficient: it tells the agent what comes back (value, WHO category, healthy range) so the return shape is not a mystery. The only gap is that the age-dependent behavior lives solely in the schema rather than being surfaced in the description.

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 boyCm, kiloKg and the optional yas are already documented, including the note that adult classification does not apply under 18. The description's phrase 'boy ve kilodan' confirms the two required inputs but adds no syntax, unit, or range detail, and omits the age parameter entirely, so it stays at the baseline for a fully documented schema.

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 gives a specific verb (hesaplar) and a precise resource (vücut kitle indeksi / BMI) and even enumerates the three results produced: BMI value, WHO category, and healthy weight range. It is unambiguous against the calculator siblings, whose names cover unrelated domains (KDV, kira, kıdem), though it never explicitly contrasts itself with any of them.

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: an agent can infer it should call this when a user supplies height and weight and wants a BMI assessment. There is no explicit when-to-use framing, no mention that the age parameter is optional or when to supply it, and no stated preconditions or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources