FlatHunt

Render FlatHunt listing cards

render_listings_widget

Read-onlyIdempotent

Return UI-ready cards and an interactive MCP Apps gallery for 1–10 FlatHunt listing ids. The tool refreshes current listing data and displays images, provider, price, availability and listing actions. Optional alertCriteria adds a saved-search control for the represented filters.

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": {
      "listingIds": "<listingIds>"
    },
    "name": "render_listings_widget"
  }
}

Input Schema

Name	Required	Description	Default
`listingIds`	Yes	Between 1 and 10 unique FlatHunt listing ids.
`alertCriteria`	No	Optional saved-search criteria represented by this result set. Every nested field is optional. Pagination and sort fields are not accepted.

Output Schema

Name	Required	Description	Default
`listings`	Yes
`alertCriteria`	No	Optional object. If present, include only the filter keys used in the preceding search_listings call — every nested field is optional; omit unused keys. Never require all fields. Do not include page, limit, sortBy, or sortOrder.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / alertCriteria / properties / postCode / description

Previous value: -"Optional. Exact Berlin PLZ from the search."New value: +"Optional. Exact post code from the search."

changedOutput schema / properties / alertCriteria / properties / postCode / description

Previous value: -"Optional. Exact Berlin PLZ from the search."New value: +"Optional. Exact post code from the search."

Changed1 schema field changedNov 9, 2026
- addedOutput schema / properties / listings / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 8, 2026
- addedOutput schema / properties / listings / items / properties / priceIsFrom
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / listings / items / properties / unitsAvailable
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / listings / items / properties / unitsTotal
```
Added value: +{
+  "type": "number"
+}
```
First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavior beyond them: it re-fetches live listing data rather than serving cached cards, and it renders specific fields plus listing actions. It does not mention latency, max refresh cost, or failure behavior for stale/missing ids.

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?

Three short sentences, front-loaded with the return shape and scope. The field list ('images, provider, price, availability and listing actions') duplicates what the output schema already conveys and could be trimmed.

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 an output schema, complete annotations, and fully documented nested parameters, the description only needs to establish purpose, scope, and the optional alertCriteria role — all of which it does. The main residual gap is sequencing relative to the search/retrieval siblings.

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% and the nested alertCriteria fields are documented exhaustively in the schema itself. The description only restates the 1–10 id bound and explains that alertCriteria drives a saved-search control, which is a small purpose-level addition rather than new semantic detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return UI-ready cards and an interactive MCP Apps gallery') with the scope bound ('1–10 FlatHunt listing ids'), which distinguishes it from single-listing and search siblings. It stops short of naming any sibling explicitly, so the differentiation is implicit.

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?

'refreshes current listing data' hints this is the render step after a search or retrieval, but there is no explicit when-to-use/when-not guidance and no named alternative such as get_listing or search_listings. The agent must infer the call sequence.

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

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