Skip to main content
Glama
Sign In
Aura Courier MCP

Aura Courier MCP

by auraajenticai
OverviewSchemaSourceRelated ServersDiscussionsAdmin

create_parcel

Book and dispatch a physical parcel across Bangladesh via supported couriers, creating a billable shipment and official tracking code. Use only after verifying recipient address and phone.

Instructions

Book and dispatch a physical parcel consignment across Bangladesh through Steadfast, Pathao, RedX, Paperfly, or AI smart cascading routing. STATE-MUTATING ACTION: This call creates a real, billable shipment record in the carrier's production database, assigns an official tracking code, and deducts courier fees upon pickup. Once booked, cancellations require direct courier portal operations. Use only after customer address and phone number are verified. Do NOT use for preliminary fee estimation (use 'calculate_delivery_zone_and_fee' or 'compare_courier_rates') or address validation (use 'validate_and_geocode_address'). Throws an error if required courier credentials are not configured or recipient phone is invalid.

Input Schema

NameRequiredDescriptionDefault
noteNoSpecial instructions for delivery rider
valueNoDeclared parcel value in BDT (used by RedX; defaults to the COD amount)
courierNoTarget courier or 'auto' for AI smart routing (default: auto)
invoiceYesUnique order invoice number (e.g. INV-1002)
item_typeNoWhat's inside the parcel (used by RedX)
cod_amountYesCash on delivery amount in BDT (0 if prepaid)
item_weightNoParcel weight in KG (default: 0.5)
recipient_nameYesCustomer full name
pickup_store_idNoRedX only: your pickup store id (optional)
recipient_phoneYes11-digit Bangladeshi mobile number (e.g. 017XXXXXXXX)
delivery_area_idNoRedX only: numeric delivery-area id (auto-resolved from the address if omitted)
recipient_addressYesDelivery address (Thana, District, Street)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed24 schema fields changedv2.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / codAmount
      Removed value: -{
-  "description": "Cash-on-delivery amount in BDT (0 = prepaid).",
-  "minimum": 0,
-  "type": "number"
-}
    • addedInput schema / properties / cod_amount
      Added value: +{
+  "description": "Cash on delivery amount in BDT (0 if prepaid)",
+  "type": "number"
+}
    • removedInput schema / properties / courier / default
      Removed value: -"steadfast"
    • changedInput schema / properties / courier / description
      Previous value: -"Which courier to book with."New value: +"Target courier or 'auto' for AI smart routing (default: auto)"
    • changedInput schema / properties / courier / enum
      Previous value: -[
-  "steadfast",
-  "pathao",
-  "redx",
-  "paperfly"
-]New value: +[
+  "steadfast",
+  "pathao",
+  "redx",
+  "paperfly",
+  "auto"
+]
    • addedInput schema / properties / delivery_area_id
      Added value: +{
+  "description": "RedX only: numeric delivery-area id (auto-resolved from the address if omitted)",
+  "type": "number"
+}
    • changedInput schema / properties / invoice / description
      Previous value: -"Your unique order/invoice id (idempotency key)."New value: +"Unique order invoice number (e.g. INV-1002)"
    • removedInput schema / properties / invoice / minLength
      Removed value: -1
    • removedInput schema / properties / itemDescription
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / item_type
      Added value: +{
+  "description": "What's inside the parcel (used by RedX)",
+  "type": "string"
+}
    • addedInput schema / properties / item_weight
      Added value: +{
+  "description": "Parcel weight in KG (default: 0.5)",
+  "type": "number"
+}
    • removedInput schema / properties / meta
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Courier-specific extras. Pathao: { storeId, cityId, zoneId, areaId }.",
-  "type": "object"
-}
    • addedInput schema / properties / note / description
      Added value: +"Special instructions for delivery rider"
    • addedInput schema / properties / pickup_store_id
      Added value: +{
+  "description": "RedX only: your pickup store id (optional)",
+  "type": "number"
+}
    • removedInput schema / properties / recipientAddress
      Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / recipientName
      Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / recipientPhone
      Removed value: -{
-  "pattern": "^01\\d{9}$",
-  "type": "string"
-}
    • addedInput schema / properties / recipient_address
      Added value: +{
+  "description": "Delivery address (Thana, District, Street)",
+  "type": "string"
+}
    • addedInput schema / properties / recipient_name
      Added value: +{
+  "description": "Customer full name",
+  "type": "string"
+}
    • addedInput schema / properties / recipient_phone
      Added value: +{
+  "description": "11-digit Bangladeshi mobile number (e.g. 017XXXXXXXX)",
+  "type": "string"
+}
    • addedInput schema / properties / value
      Added value: +{
+  "description": "Declared parcel value in BDT (used by RedX; defaults to the COD amount)",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "invoice",
-  "recipientName",
-  "recipientPhone",
-  "recipientAddress",
-  "codAmount"
-]New value: +[
+  "invoice",
+  "recipient_name",
+  "recipient_phone",
+  "recipient_address",
+  "cod_amount"
+]
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does: it discloses that this writes a real billable shipment to the carrier's production database, assigns an official tracking code, deducts fees on pickup, and that cancellation afterward requires courier portal operations. It also names two failure modes (missing courier credentials, invalid recipient phone), which is unusually complete for a mutation tool.

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?

Front-loaded with purpose and carrier scope, then the mutation warning, then preconditions, then alternatives, then error conditions. Every sentence carries distinct operational information; nothing is redundant or padded.

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?

For a 12-parameter, unannotated, no-output-schema mutation tool this covers the critical ground: side effects, billing, irreversibility, prerequisites, and failure modes. The only minor gap is that, absent an output schema, it does not explicitly state what the caller receives back (e.g. the tracking code field in the response), which it only implies.

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 every parameter is already documented in the schema with types, defaults, and courier-specific notes, so the baseline of 3 applies. The description adds only a precondition on recipient phone validity and the 'auto' routing mode, neither of which extends individual parameter meaning beyond the 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 ('Book and dispatch a physical parcel consignment') and enumerates the supported carriers including 'auto' smart routing. It is immediately distinguishable from read-only siblings like compare_courier_rates and track_parcel 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 Guidelines5/5

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

Explicit preconditions are given ('Use only after customer address and phone number are verified') and named alternatives handle the adjacent cases: calculate_delivery_zone_and_fee / compare_courier_rates for fee estimation and validate_and_geocode_address for address validation. An agent has both the when and the when-not.

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