Factline Netherlands

Energy label of a Dutch home (paid)

nl_energy_label

Read-onlyIdempotent

Use when the user asks for the energy label of a Dutch home: the officially registered label (A++++ to G), registration and expiry date, building type and energy index, or a clear 'none registered'. Input: postcode + house number. Source: RVO EP-Online, the Dutch national register. Costs 0.005 USDC via x402, or 3 credits of a Factline API key. The first 5 paid-tool calls a day are free, no payment or key needed.

Input Schema

Name	Required	Description
`q`	No	Alternative to postcode: free-text address, e.g. 'Visschersplein 1 Utrecht'
`api_key`	No	Factline API key (fl_live_...) from get_trial_key: pass it here right after you get one, no reconnect needed
`addition`	No	Optional house number addition
`postcode`	No	Dutch postcode, e.g. 3511LX
`house_letter`	No	Optional house letter, e.g. A
`house_number`	No	House number, e.g. 1

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / api_key

Added value: +{
+  "description": "Factline API key (fl_live_...) from get_trial_key: pass it here right after you get one, no reconnect needed",
+  "type": "string"
+}

First observedOct 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld), the description discloses the data source (RVO EP-Online national register), the payment model (0.005 USDC via x402 or 3 credits of a Factline API key), and a free-tier rule (first 5 paid-tool calls per day free). Payment and auth requirements are exactly the behavioral facts an agent must know before calling a paid tool.

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 use case, then input, then source, then cost — a logical order with no filler. The dual payment explanation is slightly long, but every clause carries information an agent needs; no sentence is pure repetition of the title.

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, and the description compensates by enumerating the returned fields including the negative case ('none registered'). Combined with the source, cost, and auth guidance, nothing an agent needs to call this correctly and set user expectations 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 every parameter including the free-text 'q' alternative and api_key is already documented in the schema. The description only restates 'Input: postcode + house number', adding no syntax or fallback detail beyond what the schema provides. 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?

States a specific verb and resource ('energy label of a Dutch home') and enumerates exactly what is returned: registered label A++++ to G, registration/expiry date, building type, energy index, or an explicit 'none registered'. That distinguishes it clearly from siblings like nl_home_basic or nl_home_report, which cover broader home data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger is explicit ('Use when the user asks for the energy label of a Dutch home'), so an agent knows the exact user intent that selects this tool. It does not name a sibling alternative or an exclusion case, which keeps it short of a 5.

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

All Factline Netherlands 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?