Skip to main content
Glama

Calculate Rental Profitability

calculate_rental_profitability
Read-onlyIdempotent

Compute net rental profitability after taxes and charges. Use for real estate investment analysis. Inputs: purchase price, monthly rent, charges, vacancy %, tax bracket. Returns net yield % and cash flow. See list_bundles for related 'immobilier' calculators.

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": {
      "purchase_price": "<purchase_price>",
      "monthly_rent": "<monthly_rent>",
      "monthly_charges": "<monthly_charges>",
      "annual_tax": "<annual_tax>"
    },
    "name": "calculate_rental_profitability"
  }
}

Input Schema

NameRequiredDescriptionDefault
annual_taxYesAnnual property tax in EUR
monthly_rentYesMonthly rental income in EUR
purchase_priceYesPurchase price in EUR
monthly_chargesYesMonthly charges/expenses in EUR
notary_fees_pctNoNotary fees as % of price (default 8)

Output 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).
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "formula": {
      +      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
      +      "type": "string"
      +    },
      +    "reference_url": {
      +      "description": "Link to a calcul2 page documenting the calculation in detail.",
      +      "type": "string"
      +    },
      +    "result": {
      +      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
      +    },
      +    "source": {
      +      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the 'after taxes and charges' scope framing but discloses no tax assumptions, currency handling, or rounding behavior beyond that; a 3 reflects modest added value over the annotations.

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?

Three short sentences, front-loaded with the core purpose, with no padding. The trailing 'See list_bundles' pointer is compact and earns its place as a discovery aid, though the inaccurate input list slightly undermines the structure.

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?

An output schema exists, so return values need not be re-explained, and annotations cover the safety profile. But the description's input inventory conflicts with the actual schema and gives no differentiation from the rental-yield siblings, leaving meaningful gaps for a 5-parameter financial computation.

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 100%, so the baseline is 3, but the description actively misstates the parameter set: it lists 'vacancy %' and 'tax bracket', neither of which exists in the schema, and omits notary_fees_pct (default 8), which does. This is worse than saying nothing, since an agent may hunt for non-existent inputs.

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?

States a specific verb and resource: 'Compute net rental profitability after taxes and charges', which is clearly more than a restatement of the name. However, it never distinguishes itself from the very close siblings calculate_rental_yield, calculate_rental_yield_gross, and calculate_rental_yield_net, which an agent could easily confuse with this tool.

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?

'Use for real estate investment analysis' is a broad context, not real guidance. With at least four rental-yield siblings in the tool list, the description gives no when-to-use/when-not and names no alternative, leaving selection to guesswork.

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