Zazidljiva.si

Najbolj živahni kraji

get_popular_locations

Read-onlyIdempotent

Kraji z največ aktualnimi prodajnimi vnosi in povpraševanji za zazidljive parcele.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_popular_locations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`locations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "locations": {
+      "items": {
+        "properties": {
+          "active_entries": {
+            "type": "integer"
+          },
+          "place": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "locations"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedSep 25, 2026

removedInput schema / properties / area_max

Removed value: -{
-  "minimum": 0,
-  "type": "number"
-}

removedInput schema / properties / area_min

Removed value: -{
-  "minimum": 0,
-  "type": "number"
-}

removedInput schema / properties / description
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / place

Removed value: -{
-  "type": "string"
-}

removedInput schema / properties / price

Removed value: -{
-  "minimum": 0,
-  "type": "number"
-}

First observedSep 25, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds scoping context ('current' data, building-plot focus) beyond annotations, but it does not describe behavior such as result ordering, result limits, or data freshness. No contradiction with annotations.

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?

The description is a single, information-dense sentence with no filler. It directly expresses the core differentiator and complements the title rather than repeating it verbatim.

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?

For a parameterless, read-only tool with annotations and an output schema, the description is nearly sufficient: it clearly states the subject and filtering criteria. Minor gaps are the absence of result-count or ordering expectations and no routing guidance among sibling tools, but these are not critical given the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description carries no obligation to explain input semantics. The empty schema is fully covered, and the description usefully clarifies the output scope by defining what makes a location 'popular.'

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 states a concrete resource: places with the most current sales listings and inquiries for buildable plots. This is specific enough to distinguish it from broader siblings like get_market_activity or rank_municipalities, though it lacks an explicit verb such as 'returns'.

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 criteria ('most current sales entries and inquiries for building plots') imply when the tool should be used: when the agent needs popular locations for building land. However, it does not name alternative tools or provide exclusion conditions, so usage guidance is left to inference.

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

All Zazidljiva.si 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?