Skip to main content
Glama

Marketplace Settlement Payout

bpj_marketplace_settlement_payout
Read-onlyIdempotent

Reconcile a marketplace payout when commission applies to sales after refunds, with ad and shipping deductions taken separately.

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": {
      "sales": "<sales>",
      "refunds": "<refunds>",
      "commission": "<commission>",
      "ads": "<ads>",
      "shipping": "<shipping>"
    },
    "name": "bpj_marketplace_settlement_payout"
  }
}

Input Schema

NameRequiredDescriptionDefault
adsYes
salesYes
refundsYes
shippingYes
commissionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds the genuinely useful behavioral detail: the order of operations, i.e. commission is computed on sales net of refunds, with ad and shipping deductions applied separately. Gaps remain on whether the result is a single net payout figure, whether rounding rules apply, and what the deduction ordering relative to commission actually is.

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?

A single front-loaded sentence with no filler; the reconciliation purpose comes first and the calculation constraint follows. Compression costs some precision, since 'taken separately' is doing a lot of unclarified work, but nothing is wasted.

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?

There is no output schema, so the description should say what is returned (a single net payout amount, or a breakdown), yet it does not. For a five-required-parameter calculation with no output contract and no described units, the description is serviceable but leaves the agent guessing at the result shape and the exact deduction sequence.

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 0%, so the description must carry the burden. It does map all five parameters into a relationship (sales less refunds for the commission base, ads and shipping as separate deductions), which is more than the bare titles give. However, it never states units for sales/refunds/ads/shipping (currency vs. minor units), confirms commission is a percentage, or resolves whether 'taken separately' means before or after the commission line.

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?

Names a specific action and domain object: 'Reconcile a marketplace payout'. The qualifier 'when commission applies to sales after refunds' narrows the scope further, so an agent can tell this is a marketplace-settlement calculation rather than a generic payout tool. It does not explicitly contrast with any sibling, but the sibling names (leave payout liability, absence cover cost, etc.) are far enough apart that confusion is unlikely.

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 through the situational clause 'when commission applies to sales after refunds', which tells the agent the applicable scenario but gives no when-not guidance, no prerequisites, and no named alternatives for a different commission basis. Adequate but leaves the agent to infer applicability.

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.