Skip to main content
Glama

BRAINIAC Returns & Delivery Intelligence

Calculate return shipping cost

returns-delivery_return-shipping-cost-calculate
Read-onlyIdempotent

Apply one matching caller-supplied rate to a return. A missing rate is not estimated, currencies are not converted, and the result is not a refund. Price $0.04 USDC. POST /api/v1/returns-delivery/return-shipping-cost-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-shipping-cost-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
costsNocosts. Array.
statusNostatus. String.
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
Behavior4/5

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

Beyond the annotations, the description discloses the pricing model ($0.04 USDC), the x402 payment handshake, and the failure mode where an unpaid call returns payment terms and does not execute. It also constrains the computation (no estimation, no FX conversion, not a refund). What remains undisclosed is the response shape, though an output schema exists to carry it.

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, then constraints, then price and endpoint. Minor waste in restating the endpoint path already implied by the tool name, but no filler.

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 a compute endpoint with 11 optional input parameters and no required ones, an agent still lacks guidance on the minimum viable payload and how the alternate input encodings relate. Payment behavior and return values are adequately covered (output schema present), so the gap is the input composition.

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 schema already documents all 11 parameters. The phrase 'caller-supplied rate' hints that the rates array is the operative input, but the description does not explain the role of the other payload parameters (csv, json, text, file) or which combination is expected. Baseline 3 applies.

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 resource: 'Apply one matching caller-supplied rate to a return', and scopes it negatively ('not estimated', 'not a refund'). The agent can tell it computes a rate rather than issuing money, though no sibling is named explicitly for contrast.

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 exclusions ('missing rate is not estimated', 'currencies are not converted', 'not a refund') implicitly define the intended use, and the payment prerequisite is stated. However, there is no explicit when-to-use vs. an alternative tool, and no guidance on which input payload one should supply among csv/json/text/file.

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