Skip to main content
Glama

BRAINIAC Returns & Delivery Intelligence

Calculate delivery-promise variance

returns-delivery_promise-variance
Read-onlyIdempotent

Subtract the supplied promise timestamp from the supplied delivery timestamp. A missing timestamp is not filled in, and the comparison is not a carrier guarantee. Price $0.04 USDC. POST /api/v1/returns-delivery/promise-variance. 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_promise-variance"
  }
}

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
ordersNoorders. 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.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: a missing timestamp is not imputed, results are not a carrier guarantee, the call costs $0.04 USDC, and an unpaid call short-circuits to x402 payment terms without executing. That payment/auth precondition is the kind of behavioral detail annotations cannot carry. It stops short of describing the response shape, though 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?

Four short sentences, front-loaded with the core computation, then the edge-case caveats, then price/endpoint, then the payment failure mode. Every sentence carries information an agent would otherwise have to guess.

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?

With 11 top-level parameters, zero required, nested objects, and four alternative payload carriers (csv/file/json/text), the description never explains what a minimal valid call looks like or which arrays matter for the variance. The output schema and 100% coverage offset some of that, and the missing-timestamp and payment behavior are covered, but an agent still lacks a picture of the required input shape.

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 only maps meaning onto two of the eleven inputs (promised and delivered timestamps) and says nothing about the csv/file/json/text payload variants, the orders/returns/addresses/rates/rules/events arrays, or how they relate to the variance calculation.

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 computation ('Subtract the supplied promise timestamp from the supplied delivery timestamp') and even fixes the operand order, so an agent knows exactly what value is produced. It does not contrast itself with sibling calculators such as returns-delivery_return-window-calculate, so sibling differentiation is absent.

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 only implied by the computation itself; there is no explicit 'use this when...' statement, no exclusions, and no named alternative among the sibling tools. Useful conditional context is given about unpaid calls returning x402 payment terms instead of running, but that is operational guidance rather than when-to-use guidance.

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