Skip to main content
Glama

calculate_inheritance_basic

Calculate Islamic inheritance fixed shares for heirs based on estate value, spouse, children, and parents. Returns fractions and amounts per heir.

Instructions

Calculate basic Faraid (Islamic inheritance) fixed shares. spouse: 'husband', 'wife', or None. Returns share fractions and amounts per heir.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
estate_valueYes
currencyNoUSD
spouseNo
sonsNo
daughtersNo
fatherNo
motherNo
Behavior3/5

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

With no annotations, the description carries full burden. It states the tool returns share fractions and amounts per heir, which is helpful. However, it does not disclose assumptions, limitations (e.g., basic vs complete Faraid), or behavior for missing heirs, leaving gaps for a complex calculation.

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 description is very concise (two sentences), with the first sentence stating the purpose and the second adding input/output details. No superfluous text, but it sacrifices essential parameter explanations.

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?

Given the complexity of Islamic inheritance rules, 7 parameters, no output schema, and 0% schema coverage, the description is incomplete. It fails to explain how to specify heirs, defaults, or output format, making it insufficient for confident agent invocation.

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

Parameters2/5

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

Schema coverage is 0%, yet the description only explains the spouse parameter ('husband', 'wife', or None). It fails to describe other key parameters like sons, daughters, father, mother, which are critical for Faraid calculations. Users cannot infer their meaning from the description.

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?

The description clearly states the tool calculates basic Faraid fixed shares, specifying verb 'calculate' and resource 'Islamic inheritance'. It also provides input format for spouse and output type, distinguishing it from sibling tools which cover different Islamic calculations.

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

Usage Guidelines3/5

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

The description implies usage for basic Faraid calculations but provides no explicit guidance on when to use versus alternatives or when not to use. It does not mention exclusions or limitations, though the tool appears unique among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ahmedeltaher/azan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server