Skip to main content
Glama
Sign In
glongus-mcp

glongus-mcp

by glongusmain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Mark a return as sent back (buyer)

mark_return_dispatched

Record that a buyer has posted back a cancelled delivered item, capturing carrier and tracking details and starting the refund confirmation timeline.

Instructions

Buyer only, after cancel_purchase on a delivered item: record that your owner has posted it back. carrier and tracking_number are required for posted returns (they are your owner's proof); leave both out only for a collection item handed back in person. The full refund follows when the seller confirms it arrived, or automatically 14 days after this. Requires GLONGUS_API_KEY.

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "mark_return_dispatched"
  }
}

Input Schema

NameRequiredDescriptionDefault
carrierNoLowercase carrier, e.g. "royal_mail", "evri", "dpd_uk"
transaction_idYesTransaction id
tracking_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the mutation flag profile (readOnly=false, destructive=false, openWorld=false); the description goes further by disclosing the auth requirement (GLONGUS_API_KEY) and the downstream consequence: refund on seller confirmation, or automatically after 14 days. That is real behavioral context an agent cannot get from the structured fields.

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?

Three sentences, front-loaded with the role and trigger, then the parameter rule, then the outcome. It is dense but almost every clause carries decision-relevant information; the parenthetical 'they are your owner's proof' is the only mild padding.

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 3-parameter mutation with no output schema, it covers role, precondition, parameter conditionality, auth, and refund timing. It leaves out error behavior (e.g. what happens if called before cancel_purchase) and whether the action can be corrected or undone, which an agent might want before committing.

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

Parameters5/5

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

The schema marks only transaction_id as required, with no description on tracking_number, so the schema alone would mislead. The description supplies the conditional requirement rule (both carrier and tracking_number for posted returns; both omitted for collection) and frames them as the owner's proof, which is semantics 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?

The description states a specific verb and resource ('record that your owner has posted it back') and pins down the actor ('Buyer only, after cancel_purchase on a delivered item'). Combined with the title, an agent can separate this from seller-side siblings like confirm_return_received and from mark_dispatched without opening a 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?

It gives an explicit precondition (after cancel_purchase on a delivered item) and an explicit conditional split for usage: supply carrier plus tracking_number for posted returns, or omit both only for an in-person collection hand-back. That is when-to-use and when-not-to-use guidance in one place.

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