Skip to main content
Glama

BRAINIAC Returns & Delivery Intelligence

Report returns and delivery logistics

returns-delivery_logistics-report
Read-onlyIdempotent

Combine supplied exceptions, failed-order groups, address structure, return rates, promise variance, and the return window. The report does not contact a carrier or grant a refund. Price $0.12 USDC. POST /api/v1/returns-delivery/logistics-report. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "returns-delivery_logistics-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
ratesNorates, array. Optional.
rulesNorules, array. Optional.
eventsNoevents, array. Optional.
ordersNoorders, array. Optional.
windowNowindow, object. Optional.
returnsNoreturns, array. Optional.
addressesNoaddresses, array. Optional.

Output Schema

NameRequiredDescriptionDefault
costsNocosts. Array.
itemsNoitems. Array.
levelNolevel. String.
ordersNoorders. Array.
statusNostatus. String.
totalsNototals. Array.
reasonsNoreasons. Array.
returnsNoreturns. Array.
signalsNosignals. Array.
findingsNofindings. Array.
addressesNoaddresses. Array.
checkedAtNocheckedAt. String.
lateCountNolateCount. Number.
orderCountNoorderCount. Number.
failedCountNofailedCount. Number.
limitationsNolimitations. Array.
outsideCountNooutsideCount. Number.
patternCountNopatternCount. Number.
refundGrantedNorefundGranted. Boolean.
eventsInventedNoeventsInvented. Boolean.
calculatedCountNocalculatedCount. Number.
returnInitiatedNoreturnInitiated. Boolean.
carrierContactedNocarrierContacted. Boolean.
addressIssueCountNoaddressIssueCount. Number.
deliverabilityConfirmedNodeliverabilityConfirmed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the paid-call model ($0.12 USDC), the transport (POST /api/v1/returns-delivery/logistics-report), and critically the failure mode: an unpaid call returns x402 payment terms and does not run. It also bounds side effects ('does not contact a carrier or grant a refund'), which reinforces the readOnly/non-destructive hints with concrete scope limits.

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?

Four short sentences, front-loaded with the aggregation scope, then constraints, then price and endpoint, then the payment failure behavior. No filler and no repetition of schema or annotation content.

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 an 11-parameter aggregation tool with a rich output schema and strong annotations, the description covers purpose, cost, endpoint, and payment failure adequately. The one omission is guidance on the four alternative input carriers (csv, json, text, file) and whether they are mutually exclusive, which an agent would need to choose correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic meaning by naming what the payloads represent (exceptions, failed-order groups, address structure, rates, promise variance, return window) rather than leaving them as generic 'events/orders/addresses' arrays. It does not explain the csv/json/text/file input alternatives, which is the remaining gap.

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 uses a specific verb ('Combine') and enumerates the exact inputs it aggregates (exceptions, failed-order groups, address structure, return rates, promise variance, return window), which maps cleanly onto the sibling analysis tools. It is clear this is an aggregation/report tool rather than a single-purpose analyzer, though it never names a sibling 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?

The phrase 'Combine supplied ...' implies this is a downstream step that consumes the outputs of the individual analyses, but the description never states when to use this versus calling the sibling tools directly, nor any prerequisite ordering. Usage is inferable but not spelled out.

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