Skip to main content
Glama

Chargeback Dispute Value

bpj_chargeback_dispute_value
Read-onlyIdempotent

Estimate incremental recovery from contesting a chargeback after administrative cost and an extra fee payable only if the contest fails.

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": {
      "win": "<win>",
      "recovered": "<recovered>",
      "admin": "<admin>",
      "dispute": "<dispute>"
    },
    "name": "bpj_chargeback_dispute_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
winYes
adminYes
disputeYes
recoveredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuine behavioral detail — the 'dispute' fee is charged only when the contest fails, while admin cost applies regardless — but says nothing about the return value's form (a single net amount) or rounding/currency handling.

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?

A single sentence with no filler, front-loaded with the outcome being estimated and followed by the cost conditions that make the estimate non-obvious. Every clause earns its place.

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

Completeness4/5

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

For a four-input pure calculator with annotations covering side effects and no output schema, the description supplies the essential cost semantics an agent needs before filling parameters. It could be complete with one clause stating that the result is a net monetary figure.

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?

With 0% schema description coverage, the description carries the burden, and it successfully disambiguates the cost model: admin cost is unconditional, the dispute fee is conditional on failure, and recovery depends on winning. The win-probability input is only implied rather than stated, and no units are given, so it stops just short of full coverage.

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 verb ('Estimate') and a precise resource ('incremental recovery from contesting a chargeback'), which is enough to distinguish it from the other bpj_* financial calculators. It stops short of explicitly naming a sibling or boundary case, so it is clear rather than differentiating.

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: the reader infers this is for deciding whether contesting a chargeback is worth it. There is no explicit when-to-use, when-not-to-use, or comparison to an alternative such as a plain recovery or cost tool.

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.