Skip to main content
Glama

CalcBright Calculators

Zakat Calculator

zakat_calculator
Read-onlyIdempotent

AED 63,000 of savings, gold and shares owes AED 1,575 in zakat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zakat_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
cashNoCash & bank balances At home, in accounts and wallets
goldNoValue of gold Market value of gold you own
basisNoNisab basissilver
debtsNoDebts & bills due now Immediate liabilities only – not the full balance of long-term loans
silverNoValue of silver
weightsNoNisab weights South Asian and UK bodies use the tola weights; most Arab and Gulf fatwa bodies use 85 g and 595 g.tola
businessNoBusiness assets Stock for sale and business cash
currencyNoCurrencyUSD
goldPriceNoGold price per gram (24k) Leave empty to use today’s live market price, or type your local price.
investmentsNoInvestments & shares Market value of shares, funds, crypto
receivablesNoMoney owed to you Loans you expect to be repaid
silverPriceNoSilver price per gram Leave empty to use today’s live market price, or type your local price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / weights
      Added value: +{
      +  "default": "tola",
      +  "description": "Nisab weights South Asian and UK bodies use the tola weights; most Arab and Gulf fatwa bodies use 85 g and 595 g.",
      +  "enum": [
      +    "tola",
      +    "mithqal"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds nothing beyond them – it never mentions that unspecified prices fall back to live market rates, that results depend on nisab basis/weights, or that all inputs are optional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the single sentence is spent on an example output rather than the tool's function, so it does not earn its place as a description. There is no front-loaded statement of what the tool does.

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

Completeness2/5

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

For a 12-parameter calculator with no output schema, the description should explain the calculation, the handling of omitted prices, and the shape of the result. The example does hint that a single total is returned, which is the only useful signal, but behavior around defaults and currency is entirely undocumented.

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% across all 12 parameters, so the schema carries the semantics and the baseline of 3 applies. The description only glancingly touches three input categories (savings, gold, shares) and explains none of the enums, defaults, or the goldPrice/silverPrice fallback.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is an illustrative result sentence ("AED 63,000 ... owes AED 1,575") rather than a purpose statement. An agent must infer that the tool computes zakat on cash, gold and shares; no verb or scope is stated, and nothing distinguishes it from 'calculate' or 'find_calculator'.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no routing to or from any alternative calculator sibling. The example implicitly suggests a zakat obligation context, but that is inference, not guidance.

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