CalcBright Calculators

Zakat Calculator

zakat_calculator

Read-onlyIdempotent

AED 63,000 of savings, gold and shares owes AED 1,575 in zakat. Check today’s gold or silver nisab live in your currency, with 85 g or 87.48 g weights. Web page: https://calcbright.com/zakat-calculator

Input Schema

Name	Required	Description	Default
`cash`	No	Cash & bank balances At home, in accounts and wallets
`gold`	No	Value of gold Market value of gold you own
`basis`	No	Nisab basis	silver
`debts`	No	Debts & bills due now Immediate liabilities only – not the full balance of long-term loans
`silver`	No	Value of silver
`weights`	No	Nisab weights South Asian and UK bodies use the tola weights; most Arab and Gulf fatwa bodies use 85 g and 595 g.	tola
`business`	No	Business assets Stock for sale and business cash
`currency`	No	Currency	USD
`goldPrice`	No	Gold price per gram (24k) Leave empty to use today’s live market price, or type your local price.
`investments`	No	Investments & shares Market value of shares, funds, crypto
`receivables`	No	Money owed to you Loans you expect to be repaid
`silverPrice`	No	Silver 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.

Changed1 schema field changedOct 28, 2026

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"
+}

First observedOct 12, 2026

TDQS

C2.7/5.0

Behavior1/5

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

The description repeatedly says the tool checks 'live' prices and can use 'today’s live market price,' which implies an external/open-world data source. That conflicts with the annotation openWorldHint=false, so this is an annotation contradiction; otherwise the annotations already cover read-only and idempotent behavior.

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

Conciseness3/5

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

It is short, but it front-loads a specific numeric example rather than a direct definition, and the webpage URL adds little value for tool invocation. The useful behavioral context is present but not cleanly structured.

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?

The schema is rich with 100% parameter descriptions, and the example hints at output. However, for a 12-parameter calculator with no output schema, the description does not explain the return values, whether live prices are fetched externally, or what happens when prices are omitted.

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 coverage is 100%, so the key parameter meanings are already documented. The description adds useful context about live price defaults and nisab weights, but its '85 g or 87.48 g' phrasing is confusing and does not cleanly align with the schema's tola/mithqal descriptions.

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 zakat, nisab, gold/silver, and currency, and the worked example makes clear that the tool computes an amount owed from assets and liabilities. It is understandable despite not opening with a clean 'calculate zakat due' statement, and no sibling tool overlaps with zakat calculation.

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 explicit guidance on when to use this tool versus alternatives, nor any when-not-to-use conditions. Usage is only implied by the example and nisab reference.

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

All CalcBright Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?