FlatHunt

Compare listings

compare_listings

Read-onlyIdempotent

Return normalized detail fields for 2–10 FlatHunt listings by numeric id in one read-only response. Includes prices, location, amenities, rental-policy flags, capacity, description, utilities, nearby distances, provider and tracking URLs for side-by-side comparison.

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": "compare_listings"
  }
}

Input Schema

Name	Required	Description	Default
`listingIds`	Yes	Between 2 and 10 unique listing ids.

Output Schema

Name	Required	Description	Default
`listings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026
- addedOutput schema / properties / listings / items / properties / cityId
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / listings / items / properties / cityName
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / listings / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
Changed6 schema fields changedNov 8, 2026
- addedOutput schema / properties / listings / items / properties / allInclusiveRent
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / listings / items / properties / brand
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / listings / items / properties / moveInDays
```
Added value: +{
+  "items": {
+    "type": "number"
+  },
+  "type": "array"
+}
```
- 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 declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description still adds real value beyond that: results are 'normalized' (consistent fields across providers) and delivered 'in one read-only response', which tells the agent this is a batched single round-trip rather than N separate fetches. It stops short of stating behavior for unknown or duplicate ids and result ordering.

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?

Two sentences, front-loaded with the core action and scope, with the field inventory relegated to the second sentence where it belongs. The field enumeration is slightly list-like and partly duplicates the output schema, but it is compact and earns its place by signaling comparison coverage.

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 present, return-value explanation is optional, and annotations cover the safety profile, so the definition is close to complete. The remaining gaps are edge-case behavior (invalid, missing, or duplicate ids; result ordering) rather than anything that would block a correct invocation.

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% and the single parameter already documents 'Between 2 and 10 unique listing ids' with minItems/maxItems enforced. The description restates the same 2–10 range and adds only the qualifier 'numeric id', which is already implied by the integer type. Baseline 3 applies since the schema carries the semantics.

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?

The description opens with a specific verb and resource ('Return normalized detail fields for 2–10 FlatHunt listings by numeric id') and states the batching scope plus the read-only nature. It implies the contrast with single-listing retrieval ('side-by-side comparison'), but never names get_listing or search_listings, so sibling differentiation is left to inference.

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 phrase 'for side-by-side comparison' and the 2–10 id constraint imply when this tool is appropriate (multi-listing detail retrieval in one call), but there is no explicit when-not guidance and no named alternative such as using get_listing for a single id. Usage is inferable rather than stated.

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?