Skip to main content
Glama

kapruka_gift_countries

Read-onlyIdempotent

List the countries Kapruka delivers gifts IN (international gift stores).

Use when the RECIPIENT is outside Sri Lanka — e.g. "send flowers to my sister in
Dubai", "a cake for my son in Melbourne". These gifts are delivered by Kapruka's
partner in that country, not shipped from Sri Lanka. They are NOT in
kapruka_search_products; list a store with kapruka_gift_country_products.

For each country: how many gifts are in stock now (0 = nothing can be ordered
there right now — say so), the delivery fee (one fee per order, whatever the
number of items), and for Australia and the UAE the zones they deliver to —
delivery is ONLY to those zones, each with its own fee. The earliest delivery
date is 3 days from today (Sri Lanka date).

Args:
    params: currency ('LKR' default or 'USD'), response_format.

Returns:
    str. JSON: {"currency", "earliest_date", "countries": [{"country", "products_in_stock",
    "delivery_fee": {"amount","currency"}, "zone_required": bool,
    "zones": [{"name","delivery_fee"}], "earliest_date", "store_url"}]}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the safety annotations by disclosing the partner-fulfilment model (not shipped from Sri Lanka), the meaning of products_in_stock=0, fee-per-order semantics, the zone-restricted delivery for Australia/UAE, and the 3-day earliest-delivery policy.

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?

Dense but front-loaded: purpose, then when-to-use, then behavioral rules, then Args/Returns. Slightly long with heavy formatting, but nearly every sentence carries operational information.

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?

Covers routing, edge cases (zero stock, zone-only delivery), and even the return shape (though an output schema exists), leaving no gap an agent would need to call the tool 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 description coverage is low, but the description restates both args (currency default LKR/USD, response_format) and adds the note that GBP/AUD/EUR are surfaced as USD, which is real semantics beyond the bare schema.

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 ('List the countries Kapruka delivers gifts IN') and immediately scopes it as international gift stores, which differentiates it from kapruka_list_delivery_cities and kapruka_search_products.

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

Usage Guidelines5/5

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

Explicitly says when to use it (recipient outside Sri Lanka) with concrete examples, and names the two alternatives: kapruka_search_products (where these gifts do NOT appear) and kapruka_gift_country_products (to drill into a store).

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.