Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

halooglasi_serbia_scraper

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 structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says the feed is real-time and structured, but does not disclose rate limits, authentication needs, pagination behavior, scraping freshness, or what gets returned.

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?

The description is short but highly repetitive, naming "Halooglasi Scraper - Serbia Real Estate & Cars" and then defining the tool as a feed for that same name. It is front-loaded but wastes space on circular phrasing instead of useful detail.

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?

For a scraper with no annotations and no output schema, the description is too thin to tell an agent what data fields or item types will be returned. It gives only the source domain and a generic "structured data extraction" label, leaving key operational context missing.

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?

The single parameter maxResults is fully documented in the schema as the maximum number of structured items to extract. The description adds no additional meaning beyond that schema description, so the baseline of 3 applies for high schema coverage.

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

Purpose3/5

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

The description identifies the source domain as Halooglasi Serbia real estate and cars and says it provides structured extraction data, so the broad purpose is inferable. However, it never states the specific scraping action or what kind of items are returned, and the colon phrase largely restates the tool name rather than clarifying scope.

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 guidance on when to use this scraper instead of sibling marketplace or classifieds scrapers, nor any stated exclusions or prerequisites. The only implied usage is that it applies to Halooglasi Serbia real estate and cars data, which is not enough to route between alternatives.

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.