Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (96 Tools)

halooglasi_serbia_scraper

Read-onlyIdempotent

Halooglasi Scraper - Serbia Real Estate & Cars: Real-time structured data extraction feed for Halooglasi Scraper - Serbia Real Estate & Cars.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The phrase "real-time structured data extraction feed" adds little beyond that, and nothing is said about rate limits, result freshness, whether listings and cars are mixed in one response, or what happens when maxResults exceeds available records. With annotations carrying safety, the description still leaves the operational behavior opaque.

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

Conciseness2/5

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

It is short, but the second clause is pure tautology that repeats the tool name verbatim after the colon. There is no front-loaded statement of what a call produces, and every sentence after the name is wasted space rather than useful compression.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of telling the agent what records look like, yet it never names a single returned field, whether listing type (sale/rent) or vehicle vs. property is distinguishable, or how results are ordered. For a scraper whose output shape is entirely undocumented, this is a significant gap even though the input surface is trivial.

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% with a single optional maxResults parameter whose default and meaning are documented in the schema. The description adds no filtering, sorting, or pagination semantics beyond that. Baseline 3 applies because the schema does all the work and the description contributes nothing extra.

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

Purpose2/5

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

The description is a near-verbatim restatement of the tool name and annotation title: "Halooglasi Scraper - Serbia Real Estate & Cars: ... feed for Halooglasi Scraper - Serbia Real Estate & Cars." An agent learns the source site and the two verticals (real estate, cars) only because they are embedded in the name itself. It never states what a call actually returns or how the two verticals are separated, so it does not distinguish this tool from Balkan classifieds siblings such as bolha_scraper, njuskalo_scraper, or kupujemprodajem_scraper.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no mention of which queries or geographies are supported, no prerequisites, and no pointer to a sibling for other markets or verticals. The only implicit signal is that this targets Serbia via Halooglasi, which comes from the name rather than the description text. An agent must guess whether this is the right scraper among the many regional classifieds tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources