normhyra

Exportera hyreslista som PDF

export_rent_roll_pdf

Konvertera en hyreslista (valfritt antal lägenheter, ingen övre gräns) till normhyra OCH generera en PDF-sammanställning – samma layout som PDF-exporten på normhyra.ai (liggande A4, tabell per lägenhet, sammanfattning). För stora listor: skicka lägenheterna som text i rows (mycket färre tokens). Svaret innehåller bara länk och sammanfattning, inte alla rader. Begränsat till 20 PDF:er per IP-adress och timme samt 500 per dygn totalt. Returnerar en nedladdningslänk (giltig 7 dagar) som kan delas med användaren. PDF:en innehåller källhänvisningen "Powered by Normhyra.ai – en produkt av Hyran.ai". 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. Rader med blockerande fel får error och inget resultat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_rent_roll_pdf"
  }
}

Input Schema

Name	Required	Description
`rows`	No	Kompakt alternativ till apartments – rekommenderas för stora hyreslistor (sparar tokens). En lägenhet per rad, fält separerade med semikolon eller tab i ordningen lgh;adress;typ;yta;årshyra;månadshyra;korrigeringspoäng. Tomma fält tillåts (t.ex. ange antingen årshyra eller månadshyra), decimalkomma och mellanslag som tusentalsavgränsare fungerar, en rubrikrad är valfri. Exempel: "1101;Nybrogatan 63;2 rok;58,5;98400;;0". Ange apartments ELLER rows.
`apartments`	No	Lista med lägenheter som objekt. För stora listor, använd rows i stället.
`projectName`	No	Valfritt projektnamn, visas i PDF-rubriken.
`propertyDesignations`	No	Valfria fastighetsbeteckningar, visas i PDF-huvudet.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 8, 2026

changedInput schema / properties / apartments / description

Previous value: -"Lista med lägenheter (max 500 per anrop)."New value: +"Lista med lägenheter som objekt. För stora listor, använd rows i stället."

removedInput schema / properties / apartments / maxItems
```
Removed value: -500
```
removedInput schema / properties / apartments / minItems
```
Removed value: -1
```

addedInput schema / properties / rows

Added value: +{
+  "description": "Kompakt alternativ till apartments – rekommenderas för stora hyreslistor (sparar tokens). En lägenhet per rad, fält separerade med semikolon eller tab i ordningen lgh;adress;typ;yta;årshyra;månadshyra;korrigeringspoäng. Tomma fält tillåts (t.ex. ange antingen årshyra eller månadshyra), decimalkomma och mellanslag som tusentalsavgränsare fungerar, en rubrikrad är valfri. Exempel: \"1101;Nybrogatan 63;2 rok;58,5;98400;;0\". Ange apartments ELLER rows.",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "apartments"
-]
```

Changed2 schema fields changedAug 27, 2026

changedInput schema / properties / apartments / items / properties / monthlyRent / description

Previous value: -"Månadshyra i kronor (räknas om till årshyra ×12)."New value: +"Månadshyra i kronor. Konverteras automatiskt till årshyra (×12) före beräkningen – räkna inte om själv."

changedInput schema / properties / apartments / items / properties / yearlyRent / description

Previous value: -"Årshyra i kronor. Ange yearlyRent ELLER monthlyRent."New value: +"Årshyra i kronor. Ange yearlyRent ELLER monthlyRent (minst ett krävs per lägenhet)."

First observedJul 16, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With annotations giving only a safety profile, the description adds unusually rich operational detail: rate limits (20 PDFs/IP/hour, 500/day total), that the response contains only a link plus summary and not all rows, a 7-day link validity, the attribution field contract, and the warnings/error semantics for unusual or blocking values. An agent knows exactly what it will get back and what constraints apply.

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?

Front-loaded with the core action, and the dense paragraphs are mostly information-bearing. There is mild redundancy: the attribution is stated twice (once for the PDF footer, once as a response field) and the response shape is described in two separate sentences, which slightly dilutes an otherwise tight structure.

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?

No output schema exists, so the description carries the full burden of describing return values, and it does: download link with validity, summary-only response, attribution field, warnings list interpretation, and error-row behavior. Combined with rate limits and layout expectations, nothing important for correct invocation or interpretation 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 the schema already documents rows, apartments and their fields, including the semicolon/tab ordering example and the yearlyRent-vs-monthlyRent rule. The description adds only marginal semantics ("valfritt antal lägenheter, ingen övre gräns" and the rows-for-large-lists hint), so the baseline of 3 applies.

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 names concrete verbs and resources: convert a rent roll into normhyra AND generate a PDF compilation, with the exact layout specified (landscape A4, table per apartment, summary). This is unmistakably distinct from the calculate_* siblings, and the explicit output artifact (PDF + download link) makes the tool's role unambiguous.

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?

It gives real usage guidance within the tool (use rows instead of apartments for large lists to save tokens), which is useful context. However, it never says when to pick this tool over calculate_rent_roll or calculate_actual_rent, nor any when-not-to-use condition, so sibling routing is left implicit.

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

All normhyra 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?