Skip to main content
Glama

BRAINIAC Returns & Delivery Intelligence

Detect failed-delivery patterns

returns-delivery_failed-pattern-detect
Read-onlyIdempotent

Group supplied failed, undeliverable, refused, or returned orders by postcode, address, or carrier. A pattern needs at least three orders. One failure is not a carrier finding. Price $0.05 USDC. POST /api/v1/returns-delivery/failed-pattern-detect. 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_failed-pattern-detect"
  }
}

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
levelNolevel. String.
statusNostatus. String.
signalsNosignals. 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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is largely covered. The description adds genuinely useful operational context the annotations cannot: the $0.05 USDC price, the POST endpoint, and that an unpaid call only returns x402 payment terms and does not execute. That payment-gating disclosure is the main value-add, but return shape and grouping output are left unaddressed.

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?

Four short sentences, front-loaded with the core action and immediately followed by the validity threshold. The endpoint and pricing sentence is justified because it changes call behavior, though the raw path adds little for an agent that already has the tool bound.

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 tool with nested objects, rich annotations and an output schema, the description covers purpose, data threshold, and payment gating well. The noticeable gap is guidance on which input transport (csv vs json vs file vs text) to supply, which the schema labels but does not explain.

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% and there are 11 parameters, so the baseline is 3. The description adds meaning for the grouping keys (postcode/address/carrier) but says nothing about the four alternative input payloads (csv, file, json, text) or the window/rules/rates structures, leaving the schema to carry the load.

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 object — 'Group supplied failed, undeliverable, refused, or returned orders by postcode, address, or carrier' — which is concrete and actionable. It doesn't name a sibling tool to contrast with, so an agent must infer why this differs from returns-delivery_exception-classify or returns-delivery_logistics-report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real precondition ('A pattern needs at least three orders') and an explicit exclusion ('One failure is not a carrier finding'), which prevents a common misuse on thin data. It stops short of naming an alternative tool for the small-sample case, so a small inference gap remains.

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