Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

olx_ba_scraper

OLX.ba Scraper - Bosnia Marketplace Listings: Real-time structured data extraction feed for OLX.ba Scraper - Bosnia Marketplace Listings.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden and delivers almost nothing: it does not state that this is a read-only extraction, nor does it mention rate limits, pagination, authentication, caching, or result freshness despite claiming 'real-time'. 'Structured data extraction feed' is marketing phrasing rather than a behavioral trait an agent can act on.

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 none of it earns its place: the title is repeated twice within one sentence and the 'Real-time structured data extraction feed' clause is filler. There is no front-loaded statement of what an agent gets back or how to call it.

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

Completeness1/5

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

No output schema, no annotations, and a single loosely-specified parameter mean the description must explain what listings look like, whether results are paginated, and what 'real-time' means; it does none of this. For a scraping tool whose entire value is the shape of the returned data, the definition leaves the agent unable to predict results.

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 only one parameter (maxResults) and schema description coverage is 100%, so the schema already defines it clearly. The description adds no meaning about defaults, caps, or what counts as an 'item', so the baseline 3 applies.

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 names a concrete site and domain (OLX.ba, Bosnia marketplace listings) and implies extraction, which does distinguish it from sibling country scrapers like bolha_scraper or njuskalo_scraper. However, the second half merely restates the title verbatim ("feed for OLX.ba Scraper - Bosnia Marketplace Listings"), so the actual purpose statement reduces to 'scrapes listings from OLX.ba' — vague about what a listing contains or how results are shaped.

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 tool, when not to, or which sibling to choose for other Balkan marketplaces. The only implicit cue is the country/site pairing in the name, leaving the agent to infer usage entirely from the tool name.

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