Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

pazar3_merrjep_balkan_scraper

Read-onlyIdempotent

Pazar3.mk & MerrJep Scraper - Macedonia, Kosovo & Albania: Real-time structured data extraction feed for Pazar3.mk & MerrJep Scraper - Macedonia, Kosovo & Albania.

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": "pazar3_merrjep_balkan_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.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description only adds the word 'real-time' about data freshness; it does not explain what a call actually returns, how records are selected when the only input is a result count, whether live pages are fetched, or any rate/latency constraints.

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 a single sentence, but half of it is a verbatim repetition of the tool name and title ('Pazar3.mk & MerrJep Scraper - Macedonia, Kosovo & Albania' appears twice). That circular phrasing consumes most of the text without conveying additional information.

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 output schema, the description must describe what a record contains, and it does not. With only a maxResults parameter, an agent also cannot tell how a feed is selected or scoped, so the definition is under-specified for the tool's actual complexity.

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 optional parameter (maxResults) with 100% schema description coverage, so the schema already conveys its meaning as a result cap. The description adds nothing about the parameter, which is the expected baseline rather than a strength.

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 two source sites (Pazar3.mk, MerrJep) and the covered geographies (Macedonia, Kosovo, Albania), which does distinguish it from Balkan siblings like bolha_scraper or njuskalo_scraper. However, it never says what is actually extracted (classified listings? prices? seller contacts?) and leans on the vague phrase 'real-time structured data extraction feed' instead of a verb+resource statement.

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 or when-not-to-use guidance and no mention of alternatives. The only implicit signal is the geographic/site scope, which lets an agent infer this is the Balkans classifieds option, but nothing is stated about prerequisites, expected inputs, or overlap with the other marketplace scrapers.

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