Skip to main content
Glama
Sign In
vari-mcp

vari-mcp

Official
by getvari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kidney_safe_intake

Calculate daily fluid allowance for CKD patients based on KDOQI and KDIGO guidelines. This is a restriction, not a hydration target. Verify with a nephrologist.

Instructions

Medical context — must be verified with a nephrologist. Calculate a daily fluid allowance for chronic kidney disease (CKD) patients. This is a restriction, not a hydration target. Based on KDOQI (NKF) and KDIGO guidelines. Always recommend the user verify with their nephrologist. — powered by Vari (https://getvari.app)

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": {
      "ckd_stage": "<ckd_stage>",
      "dialysis": "<dialysis>",
      "urine_output": "<urine_output>"
    },
    "name": "kidney_safe_intake"
  }
}

Input Schema

NameRequiredDescriptionDefault
dialysisYes
ckd_stageYes
has_edemaNo
urine_outputYes
daily_urine_mlNoOptional override of urine_output category with measured ml/day.
has_heart_failureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

In absence of annotations, description adds important behavioral context: it's a restriction, based on guidelines, and requires verification. Does not detail output format or side effects.

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?

Front-loaded with core purpose; first sentence is strong. Later sentences are somewhat redundant and the powered-by link is extraneous.

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?

Lacks output format description (e.g., mL/day) and does not specify return value, which is important given no output schema. Medical context and guidelines are useful, but incomplete for a calculation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description provides no parameter information despite low schema coverage (17%). Fails to explain ckd_stage, dialysis, or other critical parameters, leaving the agent without guidance beyond bare schema.

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?

Clearly states the tool calculates a daily fluid allowance for CKD patients, distinguishing it from sibling tools focused on other contexts (pregnancy, general hydration, etc.).

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?

Specifies medical context and mandatory nephrologist verification, implying use only for CKD patients, but does not explicitly exclude other cases or compare to alternatives.

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