Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

BMI 体重指数计算

bmi-check

BMI 体重指数计算:按身高体重算 BMI 并对照中国成人标准分区间。纯数值计算 + WHO/中国标准参考,明确声明不是医学诊断。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "heightCm": "<heightCm>",
      "weightKg": "<weightKg>"
    },
    "name": "bmi-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
heightCmYes身高(cm)
weightKgYes体重(kg)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does real work: it calls the operation a pure numeric computation, promises a deterministic result plus its basis (依据), and explicitly disclaims medical diagnosis, which matters for a health-adjacent tool. It does not specify the exact output fields or the band boundaries returned, so the behavior is characterized in the right direction but not fully disclosed.

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?

The core computation and the usage trigger are front-loaded, and every sentence carries information. The opening 'BMI 体重指数计算' is a near-restatement of the title, and '传入参数对象,返回确定性计算结果与依据' is somewhat boilerplate, which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain what comes back; it says only '确定性计算结果与依据' without naming the BMI value, the category label, or the reference standard returned. The non-diagnostic disclaimer is a valuable addition, but the return contract stays underspecified for a tool whose whole point is a trustworthy answer.

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% and both parameters (heightCm, weightKg) carry their own unit-annotated descriptions. The description only restates '按身高体重' without adding format constraints, valid ranges, or unit edge cases, so it adds nothing beyond the 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 names a specific verb and resource ('按身高体重算 BMI 并对照中国成人标准分区间'), so the agent knows it computes BMI and classifies it using Chinese adult bands. The purpose is unambiguous, but it never contrasts this tool with sibling calculators such as gpa-convert or mortgage-monthly, so sibling differentiation depends on the caller already knowing what those tools do.

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

Usage Guidelines4/5

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

'适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案' gives the caller an explicit trigger for using this tool instead of doing the arithmetic inline. No exclusion case or named alternative is provided, which keeps it below a 5.

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