normhyra

Exportera hyreslista som PDF

export_rent_roll_pdf

Konvertera en hyreslista till normhyra OCH generera en PDF-sammanställning – samma layout som PDF-exporten på normhyra.ai (liggande A4, tabell per lägenhet, sammanfattning). 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.

Input Schema

TableJSON Schema

Name	Required	Description
`apartments`	Yes	Lista med lägenheter (max 500 per anrop).
`projectName`	No	Valfritt projektnamn, visas i PDF-rubriken.
`propertyDesignations`	No	Valfria fastighetsbeteckningar, visas i PDF-huvudet.

TDQS

A3.9/5.0

Behavior4/5

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

The description discloses concrete behavioral details beyond the annotations: the PDF layout, the 7-day link validity, the attribution text in the PDF and in every response field, and the instruction to display attribution with results. No contradictions with 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?

The description is front-loaded with the core purpose and layout, followed by return-link details and attribution requirements. Though it repeats the attribution phrase twice, each sentence adds functional information, making it appropriately concise.

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?

With no output schema, the description adequately covers the return value (download link, validity) and the required attribution field. It also specifies the PDF layout and conversion behavior. The only minor gap is that it doesn't explicitly describe error conditions, but the schema covers input constraints.

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?

The input schema already provides descriptions for all parameters and properties (100% coverage), including the automatic monthly-to-yearly conversion note for monthlyRent. The tool description adds no parameter-specific semantics beyond what the schema already provides, so baseline 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 clearly states the tool converts a rent list to norm rent and generates a PDF compilation with a specific layout ('liggande A4, tabell per lägenhet, sammanfattning'). It also specifies the return value (download link valid 7 days) and attribution requirements, distinguishing it from calculation-only siblings by focusing on PDF export.

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 use when a shareable PDF of a rent roll is needed, mentioning the download link and layout. However, it provides no explicit guidance on when to choose this over sibling tools like calculate_normhyra or calculate_rent_roll, nor any exclusion criteria.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation4/5

The tools are largely distinct: one converts normhyra to actual rent, one actual rent to normhyra for a single apartment, and two handle rent-roll batch conversions (one with PDF export). There is some conceptual overlap between calculate_normhyra and calculate_rent_roll, but the single-vs-batch distinction is clear from the descriptions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: calculate_* for computations, export_* for output generation, and list_* for reference data. The naming is predictable and makes the action of each tool immediately understandable.

Tool Count5/5

Five tools is well-scoped for a niche calculation service. Each tool covers a distinct part of the workflow: reference data, single conversion in both directions, batch conversion, and PDF export, with no redundant or bloated additions.

Completeness4/5

The core workflow is well covered: users can list apartment types, convert between actual and normhyra, process a rent roll, and export a PDF. A minor gap is that there is no batch inverse conversion (normhyra back to actual rents for multiple apartments), but this is not a critical dead end for the domain.

Resources

Need Help?