Skip to main content
Glama

BRAINIAC Returns & Delivery Intelligence

Validate shipping-address structure

returns-delivery_shipping-address-validate
Read-onlyIdempotent

Check that the supplied lines, city, postcode, and country are present, and compare a postcode with a published shape for nine country codes. The check does not confirm that a carrier can deliver. Price $0.04 USDC. POST /api/v1/returns-delivery/shipping-address-validate. 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_shipping-address-validate"
  }
}

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.
findingsNofindings. Array.
addressesNoaddresses. 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?

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds genuinely new behavior: a $0.04 USDC charge, and that an unpaid call returns x402 payment terms without executing — critical for an agent to avoid mistaking a payment challenge for a validation result. It also sets expectations on check depth.

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 what is checked and immediately followed by the key limitation and the payment/endpoint facts. No filler, though the bare POST path adds little for an agent that already knows the tool name.

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?

An output schema exists, so return values need no explanation, and the payment semantics are covered. The remaining gap is that the tool accepts 11 optional envelope parameters (orders, returns, rates, events, etc.) with no indication of which container the address must be passed in, which matters for a nested-object tool.

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 maps the check to address fields (lines, city, postcode, country) that live inside the nested addresses array, adding slight orientation, but it does not explain how the address is actually supplied across the many envelope parameters (json/csv/text/file/addresses).

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 concrete verb ('Check') and enumerates exactly what is validated: presence of lines, city, postcode, and country, plus postcode shape for nine country codes. The negative scope ('does not confirm that a carrier can deliver') sharpens the boundary, though no sibling tool is named 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?

Implies usage through the explicit non-capability (structural check only, not deliverability), which helps an agent decide between this and a carrier/label check. However, there is no explicit 'use this when...' statement or named alternative among the seven sibling tools.

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