Skip to main content
Glama

Courier claim open

courier_claim_open

[Support desk] Propose opening a claim at the courier (parcel lost, damaged, wrong cash-on-delivery amount, not delivered): a written claim from the support mailbox plus a task to follow it. 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": {
      "awb": "<awb>",
      "type": "<type>"
    },
    "name": "courier_claim_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
awbYes
typeYes
accountNoAccount id from list_accounts. Optional when only one account is connected.
order_refNo
thread_idNo
attachmentsNo
descriptionNo
courier_nameNoThe courier carrying the AWB (Cargus, Strongo, DPD), when several are connected.
declared_valueNo
amount_expectedNo
courier_accountNo
amount_collectedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / courier_name
      Added value: +{
      +  "description": "The courier carrying the AWB (Cargus, Strongo, DPD), when several are connected.",
      +  "type": "string"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the concrete side effects: a written claim is emitted from the support mailbox plus a follow-up task is created, and the operation runs in a simulated mode first. It does not warn that the tool is non-idempotent (per annotations), so duplicate claims from retries are not called out.

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?

A single dense sentence with the scope tag front-loaded and no filler. It packs purpose, side effects, and simulation mode efficiently, though the parenthetical list of claim types is somewhat compressed.

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 explained, and annotations carry the safety profile. However, for a 12-parameter mutation with 17% schema coverage, the description leaves too many inputs unexplained for an agent to populate a claim request confidently.

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 only 17% of 12 parameters; only account and courier_name carry schema text. The description maps claim types onto the type enum but says nothing about awb, order_ref, thread_id, attachments, declared_value, amount_expected, or amount_collected, which the mismatch between required and conditional fields makes risky.

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?

States a specific verb and resource ('Propose opening a claim at the courier') and enumerates the claim categories it covers (lost, damaged, wrong COD, not delivered), which matches the type enum. It does not distinguish itself from case-opening siblings such as warranty_case_open, so an agent must infer the boundary.

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 the '[Support desk]' scope tag imply when this tool applies, and 'propose' signals it is a pre-commit step rather than the final submission. There is no explicit when-not guidance or named alternative for the cases where a claim should not be opened.

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