Skip to main content
Glama
tresor4k

macalc

calculate_moroccan_profit_foncier

Compute Moroccan property income tax (profit foncier) by entering annual rental income, deductible expenses percentage, and dependents. Get taxable income, tax amount, effective and marginal rates.

Instructions

Calculate Moroccan property income tax (profit foncier / revenus fonciers). Returns: {annual_rent_mad, taxable_income, income_tax_mad, effective_rate_pct, marginal_rate_pct}. See list_bundles for related 'finance-afrique-quebec' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annual_rent_madYesAnnual rental income in MAD
expenses_pctNoDeductible expenses as % of rent (default 40%)
dependentsNoNumber of dependents for family deduction

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations provided; description implies read-only calculation but does not explicitly state no side effects. Returns structure is given.

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

Conciseness5/5

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

Two sentences, efficient, first sentence captures purpose and output.

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

Completeness4/5

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

Provides purpose and return fields; missing details on calculation assumptions or tax rates, but output schema exists.

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?

All parameters have schema descriptions; description adds output fields but no extra parameter semantics beyond 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?

Description clearly states it calculates Moroccan property income tax, distinguishing from sibling 'calculate_moroccan_income_tax'. Mentions return fields.

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?

Lacks explicit when-to-use guidance or comparison with alternative calculators. Only mentions related calculators via list_bundles, which is indirect.

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/tresor4k/macalc-mcp'

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