Skip to main content
Glama

calculate_delivery_zone_and_fee

Calculate standard delivery zone (inside_dhaka <=22km ৳80, sub_dhaka 22-45km ৳100, outside_dhaka >45km ৳150), road distance via Google Maps Platform Routes API, structured SLA hours ({min, max}), and applicable COD percentage for a single delivery destination using the unified tariff table (meta.source='static_tariff'). READ-ONLY ESTIMATION TOOL.

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": {
      "recipient_address": "<recipient_address>"
    },
    "name": "calculate_delivery_zone_and_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
weight_kgNoParcel weight in KG (default: 0.5)
origin_addressNoOptional merchant warehouse address (defaults to Dhaka Central Hub)
recipient_addressYesDelivery destination address

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?

With no annotations, the description still discloses that it is read-only, that distance comes from an external Google Maps Platform Routes API call, and that tariffs come from a static tariff table (meta.source='static_tariff'), which implies external latency and a fixed pricing source. It stops short of stating failure behavior when an address cannot be resolved.

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 core computation and all tariff tiers are front-loaded in one dense sentence, with the read-only constraint tagged at the end. The parenthetical fee table is information-dense but earns its space; the trailing all-caps label is mildly redundant with 'Calculate'.

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?

No output schema exists, so the description correctly enumerates what is returned: zone, road distance, SLA hours as {min, max}, and COD percentage. For a three-parameter estimation tool this is largely sufficient, with only error and geocoding-failure behavior left unaddressed.

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 coverage is 100% and each parameter already carries a description, so the baseline is 3. The description adds only the framing that results are computed for a single destination and against a unified tariff table, without clarifying whether weight_kg actually affects the quoted fee.

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 (Calculate) plus the exact resource set returned: delivery zone, road distance, SLA hours, and COD percentage. The three named zones with their distance bands and fees make the tool's scope unmistakable and distinguish it from parcel-mutation siblings.

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?

The phrase 'for a single delivery destination' implicitly scopes usage away from bulk operations, and 'READ-ONLY ESTIMATION TOOL' signals a pre-check role. However, it never names an alternative such as compare_courier_rates or bulk_create_parcels, nor states when quoting a fee is not appropriate.

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