Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

pazar3_merrjep_balkan_scraper

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 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 supplied, so the description carries the entire behavioral burden, and it discloses almost nothing: no indication of whether requests are paginated, throttled, cached, authenticated, or how current the 'real-time' data actually is. The single hint ('real-time') is unquantified. For a scraping tool with zero annotation coverage this leaves the agent guessing about operational behavior.

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 single sentence restates the same string twice ('Pazar3.mk & MerrJep Scraper - Macedonia, Kosovo & Albania' appears in both the leading phrase and the trailing 'for ...' clause), producing a circular, redundant statement. Nothing about extraction scope, fields, or limits is front-loaded because no such content exists.

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, no annotations, and a single optional parameter, the description is the only place an agent could learn what records look like, what fields are returned, or how large a result set is practical. It supplies none of that, leaving the definition inadequate for correct invocation beyond the default call.

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% and the sole parameter (maxResults, default 10) is fully documented in the schema, so the baseline score of 3 applies. The description adds nothing about the parameter, such as a maximum cap or how results are ordered/bounded, so it neither compensates nor detracts.

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 resources being scraped (Pazar3.mk and MerrJep) and the geographies covered (Macedonia, Kosovo, Albania), and 'data extraction' implies a scraping verb. However, 'real-time structured data extraction feed' is vague about what kind of records come back (classifieds listings, presumably) and the phrasing is more marketing tagline than functional statement. An agent can infer the general domain but not the shape of the output.

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 at all on when to select this tool over the many other regional scraper siblings, nor any stated prerequisite, rate limit, or coverage limitation. The geographic and site coverage is the only implicit selector, and it is never framed as such.

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

All GMPSignal Real-Time Intelligence MCP toolsInspect
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