Bazos-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_adsA | Search ads on Bazos.cz, Bazos.sk, Bazos.at, or Bazos.pl. Returns a list of ads matching the criteria. |
| get_ad_detailB | Get detailed information about a specific ad by its ID. |
| get_user_ratingsC | Get user ratings by phone ID and/or email ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: searching ads, getting ad details, and retrieving user ratings. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (search_ads, get_ad_detail, get_user_ratings), making them predictable and easy to understand.
Three tools is slightly below average but reasonable for a focused read-only classified ads interface. The scope is appropriate, though a few more tools (e.g., list categories) could be added.
The toolset covers the core browsing workflow—search, detail view, and user ratings. Minor gaps exist (e.g., no explicit category listing or filtering), but the set is functional for typical use cases.