Skip to main content
Glama

Dukkani — Saudi groceries and grocery cashier

دوّر بقالة قريبة — Find nearby groceries (Saudi Arabia)

find_groceries
Read-onlyIdempotent

Find neighbourhood groceries (بقالات / تموينات) in Saudi Arabia from Dukkani's public directory, by district (حي) + city, by city, or by coordinates. Returns each grocery's name, city, distance (km, when known), an order_url (Dukkani order page; the customer sends the order on WhatsApp), a map_url and open (customers' open/closed confirmations of the last 3 hours, or null), plus nearest_url: the live «nearest grocery» radar for where the user is now. Groceries that use Dukkani and take orders in the app come first (on_dukkani=true). Use the Arabic district/city names when you have them (e.g. district «النهضة», city «عفيف»).

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity, e.g. الرياض، جدة، عفيف، بريدة (Arabic preferred)
limitNo
districtNoDistrict / neighbourhood (حي), e.g. الياسمين، النهضة. Give the city too when you know it.
latitudeNoOptional: the user's latitude (only if they shared it)
longitudeNoOptional: the user's longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the tool as read-only and non-destructive, but the description adds substantial behavioral detail: return fields (distance, order_url, map_url, open status from last 3 hours, nearest_url), ranking behavior (on_dukkani=true groceries first), and the WhatsApp ordering handoff. This is exactly the kind of context that helps an agent interpret results correctly.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and then layers on the lookup modes and return fields without wasting much space. It is dense but every sentence contributes relevant information, though it could be broken into shorter structured clauses for readability.

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

Completeness5/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 carries the full burden of explaining returns, and it does so thoroughly: name, city, distance, order_url, map_url, open status, nearest_url, and on_dukkani ranking. For a read-only discovery tool, this is complete enough for an agent to call and interpret results correctly.

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 coverage is already 80%, so the schema documents most parameters. The description adds useful meaning by recommending Arabic district/city names and clarifying the district+city combination and coordinate-based mode, though it does not cover the limit parameter and repeats some schema examples.

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?

The description opens with a specific verb+resource (find neighbourhood groceries) and immediately bounds the scope to Saudi Arabia and Dukkani's public directory. It also names the three supported lookup modes (district+city, city, coordinates), making it easy to distinguish from siblings like prepare_grocery_order.

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?

It gives clear usage context: lookup by district+city, by city, or by coordinates, and instructs the agent to use Arabic names. However, it does not explicitly state when to prefer this over prepare_grocery_order or list_cities, leaving the ordering flow implied rather than spelled out.

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