Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Reconcile marketplace settlement tax lines

ecommerce-profitability_settlement-tax-reconcile
Read-onlyIdempotent

Match order tax charged to settlement tax, marketplace-facilitator tax and refund lines within a tolerance and total seller vs marketplace collected tax. Price $0.03 USDC. POST /api/v1/ecommerce-profitability/settlement-tax-reconcile. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orders": "<orders>"
    },
    "name": "ecommerce-profitability_settlement-tax-reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
ordersYesorders, array. Required.
toleranceNotolerance, integer, from 0 to 9007199254740991. Required.
settlementLinesNosettlementLines, array. Required.

Output Schema

NameRequiredDescriptionDefault
totalsNototals. Object.
matchedNomatched. Number.
sourcesNosources. Array.
mismatchesNomismatches. Array.
limitationsNolimitations. Array.
unknownOrdersNounknownOrders. Array.
matchedOrderIdsNomatchedOrderIds. Array.
missingInSettlementNomissingInSettlement. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 open-world, so safety is covered. The description adds genuinely useful behavior beyond that: a $0.03 USDC price, the POST endpoint, and the key failure mode that an unpaid call returns x402 payment terms without executing. It does not describe how unmatched lines are reported, but the output schema is present to carry that.

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?

Three sentences, front-loaded with the core matching semantics before the pricing and endpoint details. The endpoint path and price are the least essential parts but are short and placed last, so nothing obstructs the main purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a read-only, idempotent computation tool with a full input schema, 100% parameter coverage, and a declared output schema. The description supplies what structured fields cannot: the payment requirement, the unpaid-call behavior, and the tolerance-based matching model. Nothing an agent needs to invoke it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns an increment by giving functional meaning the schema does not: 'tolerance' is framed as the acceptable variance in matching, and the three settlement line types (tax, marketplace-facilitator tax, refund) are tied to the matching and totaling logic. It still does not say whether tolerance is in currency units or whether unmatched lines fail vs. report.

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 uses a specific verb ('Match') plus a precise resource set: order tax charged versus settlement tax, marketplace_facilitator_tax, and refund_tax lines, plus a seller-vs-marketplace total. A reader knows exactly what computation runs. It does not name any sibling, but the sibling set (pricing, PPC, elasticity) is in a clearly different domain, so mis-selection risk is low.

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 operation described: use it when you have charged tax amounts and settlement lines to compare within a tolerance. There is no explicit statement of when not to use it, no prerequisite that orders and settlementLines be aligned by orderId, and no guidance on choosing a tolerance value or an alternative tool for partial-data cases.

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