Skip to main content
Glama

Get Nhif Contribution

get_nhif_contribution
Read-onlyIdempotent

Calculate the SHIF contribution for a gross monthly salary in KES, using the legacy NHIF request format when clients still reference NHIF. Returns 2.75% of gross, minimum KES 300, employee only.

Instructions

DEPRECATED NAME kept for compatibility: NHIF no longer exists. Use when a client still refers to NHIF; it returns exactly what get_shif_contribution returns plus a deprecated field, so prefer get_shif_contribution. Returns the SHIF contribution for the gross monthly salary in KES (2.75% of gross, minimum KES 300, no cap, employee only) with the source and a note to verify rates at sha.go.ke. Read-only.

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": {
      "gross_salary_kes": "<gross_salary_kes>"
    },
    "name": "get_nhif_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
gross_salary_kesYesGross monthly salary in KES.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/no-network behavior, and the description adds substantial value on top: the exact computation (2.75% of gross, min KES 300, no cap, employee only), the deprecated extra field, and the rate-verification note. Only gap is that it restates 'Read-only' already carried by readOnlyHint, and says nothing about error behavior for invalid salary values.

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 deprecation warning and preferred alternative are front-loaded, which is the right ordering for an alias tool. It is dense and largely a single run-on sentence, but every clause carries information the agent needs.

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?

For a one-parameter, output-schema-backed calculation tool, the description covers the deprecation status, the alternative, the formula, the boundaries, and the source caveat. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is fully documented, so the baseline is 3. The description goes beyond it by tying the parameter to its calculation semantics (2.75% of gross, minimum KES 300, no cap), which clarifies what the input actually means in practice.

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?

Names the resource (NHIF/SHIF contribution), states exactly what it returns, and explicitly frames itself as a deprecated alias of get_shif_contribution. An agent can distinguish it from the sibling without opening the schema.

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?

Gives an explicit when-to-use condition ('when a client still refers to NHIF') and an explicit preference ('prefer get_shif_contribution'), naming the alternative. Routing is unambiguous.

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