Skip to main content
Glama

Search listings

search_listings
Read-onlyIdempotent

Search open listings (offers) on OLTechX, the Bulgarian tech marketplace. Free-text query in Bulgarian or English (e.g. 'RTX 3060', 'iPhone 13 128GB', 'PS5'), with optional category, condition, city and EUR price range. Returns up to 24 results per page with price, condition, city and URL. When nothing matches it returns similar models that have listings, and always an alert link so the user can be notified about new matches.

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

Input Schema

NameRequiredDescriptionDefault
cityNoBulgarian city name in Cyrillic, e.g. 'София', 'Пловдив', 'Варна'
pageNo
sortNo'deal' = best price compared to the usual price for the model
queryNoFree text, e.g. 'RTX 4070', 'Ryzen 5 5600', 'MacBook Air M1'
categoryNoCategory slug from list_categories, e.g. 'videokarti', 'procesori', 'telefoni'
conditionNo
max_price_eurNo
min_price_eurNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower, and the description still adds real value: 24 results per page, the returned fields (price, condition, city, URL), fallback to similar models when nothing matches, and an always-present alert link. It omits rate limits, auth requirements, and default sort/paging behavior. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences that pack purpose, filters, return shape, fallback behavior, and alert linking, with no redundant wording. Each sentence carries distinct information.

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

Completeness4/5

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

With no output schema, the description usefully covers return fields and pagination, and it discloses the unusual no-match fallback. Remaining gaps are the unspecified optionality of 'query' and the absence of any guidance on 'sort' and 'page' defaults or limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema coverage, the description compensates by naming query, category, condition, city, and EUR price range, and adds language guidance ('Bulgarian or English') plus example queries beyond the schema. However, 'sort' and 'page' are never mentioned, and the text frames query as the central input even though all 8 parameters are optional.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Search open listings (offers) on OLTechX, the Bulgarian tech marketplace' — plus the filter dimensions, so the agent knows exactly what it retrieves. It does not name a sibling (e.g. find_models or get_model_prices) to contrast against, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: use it to find open listings by free-text query plus optional filters. There is no explicit when-to-use/when-not framing and no pointer to alternatives such as find_models for models without listings, so the agent must infer routing.

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