Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

njuskalo_scraper

Read-onlyIdempotent

Njuskalo.hr Scraper - Croatia Classifieds: Real-time structured data extraction feed for Njuskalo.hr Scraper - Croatia Classifieds.

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": "njuskalo_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/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds essentially nothing beyond that — 'real-time structured data extraction feed' hints at freshness but says nothing about source coverage, listing fields returned, pagination, rate limits, or what happens when maxResults is large.

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 almost all of that length is redundant title text repeated twice. There is no front-loaded statement of what the tool actually returns, so the brevity reflects under-specification rather than efficiency.

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?

No output schema exists, so the description is the only place return values could be described — and it only says 'structured data' without naming any listing fields (title, price, location, category, URL). For a scraper whose whole value is the shape of the extracted records, this leaves a critical gap.

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?

There is a single parameter, maxResults, and the schema already documents it at 100% coverage with a default of 10. The description adds no information about how results are ordered, whether truncation is silent, or how to page — so the baseline of 3 is appropriate rather than higher.

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 restates the tool name twice ('Njuskalo.hr Scraper - Croatia Classifieds ... feed for Njuskalo.hr Scraper - Croatia Classifieds') rather than describing the action. It does identify the resource — Croatian classifieds listings on Njuskalo.hr — but the verb is only implied by the word 'extraction' and it never distinguishes itself from the many sibling classifieds scrapers (bolha, kupujemprodajem, olx_ba, pazar3).

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no when-not-to-use, and no mention of any alternative tool. An agent must infer from the sibling names alone whether Croatian listings belong here or in a Balkan multi-country scraper.

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