Skip to main content
Glama
Sign In
GMPSignal Real-Time Intelligence MCP (59 Tools)

GMPSignal Real-Time Intelligence MCP (59 Tools)

Official
by xpayrcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

bolha_scraper

Scrape Bolha.com Slovenia classifieds for real-time structured data. Extract listings for lead generation and market research with configurable result limits.

Instructions

Bolha.com Scraper - Slovenia Classifieds: Real-time structured data extraction feed for Bolha.com Scraper - Slovenia 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": "bolha_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 full disclosure burden, yet it only offers the vague claim 'real-time structured data extraction.' It says nothing about rate limits, caching, legal/robots considerations, partial-failure behavior, or what a result record contains — all material for a scraping tool.

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 the sentence is circular: the same product-name string appears twice with a content-free filler phrase between. Nothing is front-loaded because no substantive information exists to front-load.

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?

The tool is structurally simple (one optional parameter, no nested objects, no output schema), but for a scraper the agent still needs to know what fields come back and what the site covers. With no output schema and no return-value description, the definition is under-specified for correct invocation and interpretation.

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%; maxResults is fully documented in the schema with a default of 10. The description adds no additional meaning to that parameter, so the baseline of 3 applies.

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 essentially restates the tool name twice: 'Bolha.com Scraper - Slovenia Classifieds ... feed for Bolha.com Scraper - Slovenia Classifieds.' Only 'structured data extraction' hints at the action, and there is no statement of what kind of classifieds data is returned or how it differs from sibling scrapers like njuskalo_scraper or kupujemprodajem_scraper beyond the target site.

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 guidance, no mention of alternatives, and no prerequisites or exclusions. The agent must infer from the site name alone that this is the correct scraper for Slovenian Bolha.com listings rather than one of the many other marketplace scrapers.

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

Deploy Server

Other Tools