Skip to main content
Glama
Sign In
marketua

marketua

by cuzin85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_regions

Get OLX region and city IDs for Ukraine to refine search_offers queries by location.

Instructions

List OLX regions (oblasts) and major cities with their ids, for search_offers region_id/city_id.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses the tool lists regions/cities with ids – a safe read operation. No mention of performance, caching, or region scope, but adequate for a simple lookup.

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?

Single sentence, no wasted words. Front-loaded with action and resource, and includes purpose context (ids for search_offers).

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?

Given zero params and no output schema, the description is nearly complete. It could mention whether cities are grouped under regions or are flat, but the core need (getting ids for search_offers) is met.

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?

Schema has zero parameters and coverage is 100%, so no param info needed. Description adds value by explaining the output ties to search_offers parameters.

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

Purpose5/5

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

Description states specific verb (List), resource (OLX regions and major cities), and output (ids for search_offers). Distinguishes from siblings like search_offers (which uses the ids) and list_categories.

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

Usage Guidelines4/5

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

Clear context for use – provides ids needed by search_offers. No explicit when-not or exclusions, but sibling tool names hint at alternatives.

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