Skip to main content
Glama

Dukkani — Saudi groceries and grocery cashier

جهّز طلب مقاضي — Prepare a shopping-list order

prepare_grocery_order
Read-onlyIdempotent

Turn a shopping list into a ready order for one grocery from find_groceries (pass its id, e.g. «d:82» or «b:abc12»). Returns the cleaned list and an order_url: Dukkani's order page with that grocery chosen and the list already written, so the customer only checks it and sends it on WhatsApp. This tool sends nothing by itself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grocery_id": "<grocery_id>",
      "items": "<items>"
    },
    "name": "prepare_grocery_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional note to the grocery (delivery time, «بدون سكر»…)
itemsYesList lines, e.g. «2 حليب المراعي 1 لتر», «رز 5 كيلو», «كرتون بيض»
grocery_idYesThe id returned by find_groceries (d:<number> or b:<code>)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description is consistent with them by stating explicitly that nothing is sent. It adds genuinely useful behavior beyond the annotations: what is returned (a cleaned list and an order_url pointing at the chosen grocery with the list pre-filled) and the human follow-up step on WhatsApp. Error cases and the 40-item limit are not mentioned.

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?

Three tight sentences, front-loaded with the action and followed by the return value and the safety caveat — every sentence carries information. Minor redundancy in repeating the id format already present in the schema.

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?

For a three-parameter, non-destructive tool with no output schema, the description supplies the return shape (cleaned list + order_url), the workflow context (customer reviews and sends on WhatsApp), and the safety guarantee. Nothing an agent needs to call it correctly is missing.

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?

Schema description coverage is 100%, so grocery_id, items and note are already documented with examples. The description restates the grocery_id format ('d:82', 'b:abc12') but adds no new meaning for items, note, or the ordering that 'cleaned list' implies, so this is a baseline 3.

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?

States a specific verb and resource — turn a shopping list into a ready order for one grocery — and explicitly ties the required grocery_id to the sibling find_groceries. An agent can distinguish it from find_groceries without opening either schema.

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?

Clearly says the grocery_id must come from find_groceries and gives its id format, establishing the precondition order of tool calls. It also implicitly rules out using this as the final sending step ('This tool sends nothing by itself'), though it never names an alternative tool for actually placing the order.

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