Skip to main content
Glama

Factline Netherlands

by io.github.snefhew
OverviewDiscussionsAdmin

Dutch house prices for a postcode (paid)

nl_house_prices
Read-onlyIdempotent

Use when the user asks what homes cost in a Dutch area: average home value (WOZ) in the neighbourhood with its trend, plus actual average sale prices per year in the municipality vs the national average. Context for an asking price, not a valuation of one home. Input: postcode or CBS buurt code. Source: CBS, Kadaster. Costs 0.003 USDC via x402, or 2 credits of a Factline API key. The first 5 paid-tool calls a day are free, no payment or key needed.

Input Schema

NameRequiredDescriptionDefault
codeNoAlternative: CBS neighbourhood code, e.g. BU05182245
api_keyNoFactline API key (fl_live_...) from get_trial_key: pass it here right after you get one, no reconnect needed
postcodeNoAny Dutch postcode in the neighbourhood, e.g. 2517AS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds the things they cannot: data provenance (CBS, Kadaster), an explicit price (0.003 USDC via x402 or 2 credits of a Factline API key), and a free tier (first 5 paid-tool calls a day, no payment or key). Payment and auth requirements are disclosed up front, which is exactly the extra burden a paid tool needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the trigger ('Use when...'), then the scope boundary, then input and cost. Four dense sentences with no filler; even the pricing detail earns its place because it changes whether an agent can call the tool at all.

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, and the description compensates by describing what comes back: neighbourhood WOZ with its trend, plus per-year municipal sale prices benchmarked against the national average. Combined with source attribution and full cost/auth details, an agent has everything needed to select and invoke it.

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 three parameters (postcode, code, api_key) are already documented with examples. The description's 'Input: postcode or CBS buurt code' restates what the schema says rather than adding format, fallback precedence, or validation rules. 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 resource (average WOZ home value for a Dutch neighbourhood plus yearly sale prices for the municipality vs national) and a specific verb-of-use ('asks what homes cost'). The line 'Context for an asking price, not a valuation of one home' separates it from valuation-style siblings like nl_home_report or nl_rent_check without opening any schema.

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 leading 'Use when the user asks what homes cost in a Dutch area' plus the explicit exclusion ('not a valuation of one home') gives both a trigger and a when-not. It stops short of naming the sibling tool an agent should pick instead for a single-home valuation, which keeps it from 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 toolsInspect
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