Skip to main content
Glama

BRAINIAC Returns & Delivery Intelligence

Analyze return reasons

returns-delivery_return-reason-analyze
Read-onlyIdempotent

Count supplied return reasons exactly as written. A reason is a pattern only at three or more returns. The reason text is not rewritten and no refund is granted. Price $0.04 USDC. POST /api/v1/returns-delivery/return-reason-analyze. 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_return-reason-analyze"
  }
}

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
statusNostatus. String.
reasonsNoreasons. Array.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
refundGrantedNorefundGranted. Boolean.
eventsInventedNoeventsInvented. Boolean.
returnInitiatedNoreturnInitiated. Boolean.
carrierContactedNocarrierContacted. Boolean.
deliverabilityConfirmedNodeliverabilityConfirmed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, but the description adds meaningful behavior beyond them: a $0.04 USDC price, an x402 payment gate where an unpaid call returns payment terms and does not execute, and guarantees that reason text is not rewritten and no refund is issued. That payment/authorization disclosure is exactly the kind of context an agent needs before calling.

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?

Five short sentences, front-loaded with the core operation and its threshold rule, then constraints ('not rewritten', 'no refund'), then price and endpoint. Every sentence contributes a fact an agent would otherwise have to discover.

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 tool with an output schema and full annotation coverage, the description covers purpose, threshold semantics, side-effect guarantees, and the payment flow, which is most of what matters. The remaining gap is the unstated choice among the several input channels (csv, file, json, text, structured arrays) in the 11-parameter schema.

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 description coverage is 100% across 11 parameters, so the schema documents each field. The description only obliquely references the 'supplied' return reasons and adds no format or precedence guidance for the csv/file/json/text/array input alternatives, so it stays at the baseline.

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 gives a specific verb and resource: 'Count supplied return reasons exactly as written,' with a concrete definitional rule ('a reason is a pattern only at three or more returns'). It does not name a sibling to contrast with (e.g., failed-pattern-detect), but the counting/exact-text framing is distinct enough for an agent to recognize the operation.

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?

Usage is implied rather than stated: the tool analyzes the 'supplied' returns array and applies a three-or-more threshold. There is no explicit guidance on when to pick this over failed-pattern-detect or exception-classify, nor any prerequisite about supplying the returns array versus other input channels.

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