Skip to main content
Glama

Affiliate Commission Clawback

bpj_affiliate_commission_clawback
Read-onlyIdempotent

Reconcile partner commissions charged on gross attributed sales with the reversals due for refunds and canceled sales.

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": {
      "paid": "<paid>",
      "reversed": "<reversed>",
      "commission": "<commission>"
    },
    "name": "bpj_affiliate_commission_clawback"
  }
}

Input Schema

NameRequiredDescriptionDefault
paidYes
reversedYes
commissionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. Beyond that, the description adds no behavioral detail: for a calculation tool the essential traits are the formula, sign convention (does a reversal reduce the clawback or increase it?), and what value is returned. None of these are disclosed.

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 and no redundancy. It is efficient, though its terseness is part of the reason other dimensions are thin.

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

Completeness2/5

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

For a three-required-parameter calculator with no output schema and no annotation-supplied semantics, the description should state the computation and the return value. As written, an agent knows the domain but not the arithmetic or the result shape, so it cannot confidently predict what a call yields.

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

Parameters2/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 of parameter meaning, and it largely does not. It gestures at the concepts ('gross attributed sales', 'refunds and canceled sales', commissions), which loosely maps to paid/reversed/commission, but it does not clarify that 'commission' is a percentage (0-100) rather than an amount, whether reversed is subtracted from paid, or whether the inputs are per-period totals or per-transaction.

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 names a specific domain operation with concrete resources: partner commissions on gross attributed sales reconciled against reversals for refunds and canceled sales. That is far more than a restatement of the title 'Affiliate Commission Clawback' and tells an agent this computes a clawback. It stops short of stating the actual output (net clawback amount), so the verb's result is inferred rather than declared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no exclusions or alternatives. The description never says, for example, that this applies only after a refund or cancellation has been recorded. An agent must infer the trigger condition from the phrase 'reversals due'.

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.