Skip to main content
Glama
auraajenticai

Aura Courier MCP

by auraajenticai
OverviewSchemaSourceRelated ServersDiscussionsAdmin

create_parcel

Create parcel delivery orders across Bangladesh using Steadfast, Pathao, RedX, Paperfly, or auto-selected courier. Input recipient details and COD amount to book with a normalized response.

Instructions

Book a new parcel delivery across Bangladesh (Steadfast, Pathao, RedX or Paperfly) with normalized response.

Input Schema

TableJSON 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

A3.6/5.0
Behavior2/5

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

The description only adds 'with normalized response' as a behavioral trait; everything else about side effects, prerequisites, or error behavior is left unstated. With no annotations, the description should carry more of the burden for a state-changing create operation.

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?

A single, efficient sentence with no filler; the key action and scope are front-loaded. 'Across Bangladesh' and the courier list are useful context, and 'normalized response' cues expected output.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite complete parameter docs, the description omits return-value details, side effects, and any sequencing with sibling tools. No output schema exists, so the vague 'normalized response' doesn't tell an agent what to expect after booking.

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 the schema already documents all 12 parameters. The description's mention of the four couriers and response normalization adds minimal semantic value beyond the enum and defaults already in 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?

Begins with a specific verb ('Book') and a concrete resource ('a new parcel delivery'), names the supported couriers, and adds a response-normalization guarantee. This clearly separates it from sibling tools like track_parcel, list_couriers, and get_balance.

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?

The action is unambiguous and no sibling performs creation, so an agent can infer when to call it. However, it doesn't explicitly mention that validation/rate-comparison tools (e.g., validate_and_geocode_address, compare_courier_rates) could precede booking, so usage context is clear but exclusions/ordering are absent.

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