Skip to main content
Glama

Returns create awb

returns_create_awb

[Support desk] Propose a return pickup at the customer's address: a return AWB through the courier's API (Cargus, DPD România, Strongo with an API key) or a written request to the courier's desk, the customer taken from the web shop order unless given, plus a task to follow the pickup and the reception. Simulated first. Works on: Support desk.

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": {
      "order_ref": "<order_ref>"
    },
    "name": "returns_create_awb"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
accountNoAccount id from list_accounts. Optional when only one account is connected.
contentNo
parcelsNo
customerNo
order_refYes
thread_idNo
weight_kgNo
shop_accountNo
package_openedNoWas the product unpacked (an unrolled mattress)? With several couriers, the "return_courier" policy picks the courier from this.
courier_accountNoDefault: the only courier connected, or the one the "return_courier" policy names.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / courier_account / description
      Previous value: -"Default: the only courier connected."New value: +"Default: the only courier connected, or the one the \"return_courier\" policy names."
    • addedInput schema / properties / package_opened
      Added value: +{
      +  "description": "Was the product unpacked (an unrolled mattress)? With several couriers, the \"return_courier\" policy picks the courier from this.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnly=false, destructive=false, idempotent=false). The description adds real behavioral context beyond that: the operation is simulated first, it may fall back to a written courier request, and it spawns a follow-up task for pickup and reception. It does not state permission requirements or what the simulation returns, but the added context is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded, which is good, but the single dense sentence packs courier names, fallback paths, defaults, and task creation into one run-on clause. It is information-rich but harder to parse than a short structured breakdown would be.

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?

An output schema exists, so return values need not be described, and the mutation profile is covered by annotations. Still, for an 11-parameter tool with a nested customer object and low schema coverage, several parameters and the simulation/confirmation flow are left underspecified.

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 only 27% across 11 parameters, so the description must compensate. It does explain that the customer is taken from the web shop order unless supplied, that courier_account defaults to the connected courier or the 'return_courier' policy, and that package_opened drives courier selection — but reason, content, parcels, weight_kg, thread_id, and shop_account remain unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Propose a return pickup ... a return AWB') and enumerates the two fulfillment paths (courier API vs. written request to the courier desk) plus the follow-up task. It implicitly distinguishes itself from order-AWB siblings by scoping to returns, though it never names an alternative tool explicitly.

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?

'Simulated first' and 'Works on: Support desk' give some context about when this applies, and the courier-account default is explained. However, there is no explicit when-not guidance or named alternative (e.g., orders_issue_awb, awb_get) for an agent choosing between AWB-related tools.

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