SiteCheck Jobs & Property

Hemnet homes for sale in an area: address, housing form

realestate_hemnet

Read-only

Hemnet (Sweden) homes for sale in an area: address, housing form, asking price and price per m2 (SEK), monthly fee, rooms, living area, coordinates, broker, upcoming viewings, labels, published time and link; 50 per page (pages 1-10), newest first, plus total count. The area is Hemnet's location id from a hemnet.se search URL (17744 = Stockholms lan). Via a residential proxy. Related tools on this server, for a different need: realestate_zoocasa when you need Zoocasa homes for sale in a city: MLS number, address; realestate_zoopla when you need Zoopla homes for sale or to rent in an area: headline. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "locationId": "<locationId>"
    },
    "name": "realestate_hemnet"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Results page 1 to 10 (default 1)
`locationId`	Yes	Hemnet location id (digits after location_ids[]= in a hemnet.se search URL), e.g. 17744 for Stockholms län

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses pagination limits (50 per page, pages 1-10), ordering (newest first), that a total count is returned, that requests go via a residential proxy, and the exact billing model ($0.002 USDC per successful call via x402; failed calls not charged). That is precisely the operational context annotations cannot convey.

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 resource and result fields, then the area-id convention, then sibling routing and pricing. It is dense and slightly run-on with heavy semicolon chaining, but nearly every clause carries information an agent needs.

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?

Covers scope, field list, pagination bounds, ordering, cost, and alternatives, which is complete for a two-parameter read tool with an output schema and annotations. Minor gap: no note on what happens for out-of-range pages or invalid location ids.

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 coverage is 100%: both parameters are documented, including the locationId derivation and the 17744 = Stockholms län example. The description restates those same facts rather than adding new syntax or edge-case meaning, so the 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 ('Hemnet (Sweden) homes for sale in an area') plus the returned fields, and explicitly names the sibling tools (realestate_zoocasa, realestate_zoopla) it differs from. An agent can distinguish it from other real-estate listing tools without opening the 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?

Gives a concrete routing rule ('realestate_zoocasa when you need Zoocasa homes for sale in a city', 'realestate_zoopla when you need Zoopla homes for sale or to rent in an area'), which is genuine when-to-use guidance. It lacks explicit exclusions for this tool itself (e.g., rentals in Sweden, other countries), so it stops short of full coverage.

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

All SiteCheck Jobs & Property 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?