Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

send_order_details

Send WhatsApp order details, payment, or invoice messages using an approved Utility template with an ORDER_DETAILS button for India commerce channels.

Instructions

Send a WhatsApp order details payment / invoice message using a pre-approved Utility template that has an ORDER_DETAILS button.

India only (WhatsApp Payments India). Requires:

  • India WhatsApp Business number

  • Commerce enabled on the channel (GET/POST /commerce)

  • Approved template with an ORDER_DETAILS button

Use this method when you need structured fields (order, referenceId, currency, paymentSettings). The API appends a template button sub_type: order_details and sends via the same path as POST /sendTemplate.

Works outside the 24-hour session window (template message).

You can also send the same payload yourself with POST /sendTemplate by including a button component in params:

{
  "type": "button",
  "sub_type": "order_details",
  "index": 0,
  "parameters": [{
    "type": "action",
    "action": {
      "order_details": {
        "reference_id": "order-123",
        "currency": "INR",
        "order": { "status": "pending", "items": [], "subtotal": { "offset": 100, "value": 50000 } }
      }
    }
  }]
}

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": {
      "template": "<template>",
      "namespace": "<namespace>",
      "language": "<language>",
      "order": "<order>"
    },
    "name": "send_order_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
phoneNo
chatIdNo
paramsNo
currencyNo
languageYes
templateYes
namespaceYes
referenceIdNo
paymentSettingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.10
    • changedInput schema / properties / language / additionalProperties
      Previous value: -{}New value: +false
    • addedInput schema / properties / language / properties
      Added value: +{
      +  "code": {
      +    "type": "string"
      +  },
      +  "policy": {
      +    "type": "string"
      +  }
      +}
    • removedInput schema / properties / language / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / language / required
      Added value: +[
      +  "code"
      +]
    • changedInput schema / properties / order / additionalProperties
      Previous value: -{}New value: +false
    • addedInput schema / properties / order / properties
      Added value: +{
      +  "discount": {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "items": {
      +    "items": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "amount": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "offset": {
      +              "type": "number"
      +            },
      +            "value": {
      +              "type": "number"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "quantity": {
      +          "type": "number"
      +        },
      +        "retailer_id": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "shipping": {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "status": {
      +    "type": "string"
      +  },
      +  "subtotal": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "offset": {
      +        "type": "number"
      +      },
      +      "value": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "tax": {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  }
      +}
    • removedInput schema / properties / order / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / order / required
      Added value: +[
      +  "items"
      +]
  2. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the regional restriction, commerce prerequisite, template requirement, and that the message works outside the 24-hour session window. It also explains that the API appends the order_details button, but it does not cover auth expectations, rate limits, idempotency, or error behavior.

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 description is front-loaded with purpose, region, and prerequisites before the alternative path and example. It is appropriately structured for a complex tool, though the JSON block and repeated sendTemplate explanation make it longer than strictly necessary.

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

Completeness3/5

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

Given 10 parameters, nested objects, no annotations, and no output schema, the description provides strong purpose and prerequisite context but is incomplete for invocation. It does not explain key parameters such as phone/chatId, namespace, or language, nor does it describe the response or failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, so the description needs to compensate. It names and partially explains order, referenceId, currency, paymentSettings, and params via the example, but it leaves template, namespace, language, phone, and chatId without useful semantic guidance, including how the recipient is selected.

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?

The description states a specific verb and resource: sending a WhatsApp order-details payment/invoice message via a Utility template with an ORDER_DETAILS button. It also distinguishes this path from the sibling sendTemplate route by noting that this tool is for structured order fields and that sendTemplate requires manually adding the button component.

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?

It gives explicit usage conditions: India only, India WhatsApp Business number, commerce enabled, and an approved ORDER_DETAILS template. It also names the alternative route (POST /sendTemplate with a button component in params), so an agent can choose between this method and the lower-level template send.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.