Skip to main content
Glama

normhyra

Beräkna faktisk hyra

calculate_actual_rent
Read-onlyIdempotent

Räkna om en normhyra (kr/m²/år) till faktisk årshyra i kronor för en given lägenhetstyp, yta och eventuella korrigeringspoäng. Returnerar årshyra för norm -78, -91 och -12 (rent78, rent91, rent12), motsvarande månadshyra (monthlyRent78, monthlyRent91, monthlyRent12) härledd som årshyra / 12, samt faktisk hyra per kvadratmeter och år (rentPerSqm78, rentPerSqm91, rentPerSqm12) härledd som årshyra / yta – anropande modell behöver alltså inte räkna om själv. Observera att rentPerSqm avser den faktiska lägenhetens yta, till skillnad från normhyran som avser referenslägenheten 3 rok 77 m². Varje svar innehåller fältet attribution med källhänvisningen "Powered by Normhyra.ai – en produkt av Hyran.ai", avsedd att visas tillsammans med resultatet. Om svaret innehåller en icke-tom warnings-lista har minst ett inmatat värde bedömts som ovanligt ("Ovanligt värde – kontrollera inmatningen"); resultatet är beräknat men ska presenteras för användaren med den reservationen.

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": {
      "normhyra": "<normhyra>",
      "apartmentTypeId": "<apartmentTypeId>",
      "area": "<area>"
    },
    "name": "calculate_actual_rent"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesLägenhetens yta i kvadratmeter.
normhyraYesNormhyra i kr/m²/år.
apartmentTypeIdYesId från list_apartment_types, t.ex. '2rok' eller '3rok'.
correctionPointsNoEventuella korrigeringspoäng (standard 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

With annotations covering only readOnly/idempotent/openWorld, the description adds substantial context: the exact derived outputs (monthly rent = annual/12, per-sqm = annual/area), the clarification that rentPerSqm uses the actual apartment area rather than the 3 rok 77 m² reference apartment, the mandatory attribution field, and the meaning of a non-empty warnings list. This is well beyond what the structured data provides.

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 purpose is front-loaded and the paragraph is dense with relevant information rather than filler. It is somewhat long and the aside about the calling model not needing to recalculate is slightly redundant, but every other sentence carries real information.

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

Completeness5/5

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

There is no output schema, so the description must carry the return contract – and it does, enumerating rent78/91/12, monthlyRent equivalents, rentPerSqm values, attribution, and warnings semantics. For a read-only, idempotent calculation tool nothing an agent needs is missing.

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%, so all four parameters are already documented, establishing a baseline of 3. The description restates the norms (kr/m²/år, correction points) and adds the useful note about the reference apartment, but contributes little new parameter-level guidance.

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 states a precise verb and resource: 'Räkna om en normhyra (kr/m²/år) till faktisk årshyra i kronor' for a given apartment type, area and correction points. It effectively implies the reverse direction of the sibling calculate_normhyra, but never names the sibling explicitly, so differentiation is left to inference.

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 conversion direction implies when the tool applies (you have a normhyra and need the actual rent), but there is no explicit when-to-use statement, no exclusions, and no named alternative such as calculate_normhyra or calculate_rent_roll. Usage must be inferred from the purpose sentence.

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