Skip to main content
Glama

BRAINIAC Returns & Delivery Intelligence

Calculate a return window

returns-delivery_return-window-calculate
Read-onlyIdempotent

Add the supplied day count to the supplied delivered or ordered date and compare a return request with that end date. No day count is assumed, and an inside date is not a refund entitlement. Price $0.04 USDC. POST /api/v1/returns-delivery/return-window-calculate. 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-window-calculate"
  }
}

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
daysNodays. Number.
fromNofrom. String.
statusNostatus. String.
returnsNoreturns. Array.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
daysSuppliedNodaysSupplied. Boolean.
refundGrantedNorefundGranted. Boolean.
eventsInventedNoeventsInvented. Boolean.
returnInitiatedNoreturnInitiated. Boolean.
carrierContactedNocarrierContacted. Boolean.
deliverabilityConfirmedNodeliverabilityConfirmed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 covered. The description adds behavior beyond that: no default day count is assumed, an inside-window date is explicitly not a refund entitlement, and unpaid calls short-circuit to payment terms instead of executing. Only the response/pagination behavior is left implicit, and an output schema exists.

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?

Three short sentences, front-loaded with the computation, then the semantic caveats, then the price/endpoint/payment behavior. Every clause carries information an agent needs; nothing is redundant with the title.

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?

For an 11-parameter, deeply nested payload with zero required fields, the description explains the core calculation and payment gating but not which input collections are needed versus optional context. An output schema exists, so return values need not be described. It is adequate but leaves the agent guessing about the shape of a minimal valid call.

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%, so the baseline is 3. The description ties 'supplied day count' and 'supplied delivered or ordered date' to the window.days and orders[].delivered/ordered fields, which is light added meaning. It gives no guidance on how the other payload arrays (events, rules, rates, addresses) participate, leaving the schema to carry that.

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 states a specific computation: add a supplied day count to a supplied delivered or ordered date, then compare a return request against that end date. That is a concrete verb-plus-resource statement an agent can match to a task. It does not name or distinguish itself from any sibling such as returns-delivery_return-shipping-cost-calculate, so it stops short of a 5.

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 by the described computation, and the description adds a real precondition ('An unpaid call returns the x402 payment terms and does not run') plus the $0.04 USDC price. However, it never states when to choose this over the sibling calculators, nor any exclusion or input-precondition beyond payment.

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