Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

bolha_scraper

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. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  2. 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 provided, so the description carries the full disclosure burden and largely fails it. 'Real-time' hints at live fetching, but there is no mention of rate limits, anti-bot blocking, pagination, latency, failure behavior, or what 'structured data' actually contains. For a scraping tool with zero annotation coverage this is a substantial gap.

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 it is circular: 'Bolha.com Scraper - Slovenia Classifieds' is repeated almost verbatim in the second half. The only substantive words are 'real-time structured data extraction feed,' which is vague filler rather than front-loaded 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?

The tool is structurally simple (one optional parameter, no output schema, no nested objects), so full documentation is achievable, yet the description never says what items or fields are extracted or what limits apply. An agent could invoke it but could not predict or validate its output.

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 explains it. The description adds nothing about extraction limits or defaults, but under the high-coverage rule the schema-driven baseline of 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 the source site and domain (Bolha.com, Slovenia classifieds), so the resource is identifiable, but the operative phrasing 'Real-time structured data extraction feed' is marketing filler rather than a concrete verb describing what is extracted or returned. It does not articulate what distinguishes it from site-specific scraper siblings beyond the domain name.

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 statement of when to use this tool, when not to, or what alternative to pick. Usage is only implied by the site name in the title. An agent must infer entirely from the domain that this is the Slovenian classifieds scraper versus the Croatian, Serbian, or Bosnian siblings.

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