Skip to main content
Glama

WritersLogic business agents

chargeback-fighter

E-Commerce Chargeback Representment Builder — Tells a merchant whether to fight or accept a card dispute: scores win probability against the network rubric for the reason code (Visa, Mastercard, Amex, Discover), runs deterministic Visa CE3.0 eligibility and invalid-dispute checks, computes expected recovery net of the contest fee and days to the deadline, and returns a processor-ready submission (summary under 4,000 characters, evidence field

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": {
      "network": "<network>",
      "reasonCode": "<reasonCode>",
      "orderDetails": "<orderDetails>",
      "evidence": "<evidence>"
    },
    "name": "chargeback-fighter"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkYes
evidenceYes
reasonCodeYese.g. 10.4, 13.1, 13.3 (Visa); 4837, 4853, 4855 (Mastercard).
disputeDateNo
orderDetailsYes
disputeFeeUsdNoFee your processor charges to contest the dispute and does not return on a loss; used to net the expected value.
responseDeadlineNoDeadline shown in your processor's dispute dashboard (YYYY-MM-DD); days remaining are computed from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses that the Visa CE3.0 eligibility and invalid-dispute checks are deterministic, that recovery is netted against the contest fee and deadline, and that output is a processor-ready submission with a summary capped under 4,000 characters. It does not state failure behavior, whether any judgement calls require external model calls, or permission requirements, and the output clause is cut off.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the content is dense rather than padded, which is appropriate for a multi-step tool. But it is one sprawling sentence with a dangling parenthetical and it terminates mid-token, so the structure undermines readability exactly at the point where the return format matters most.

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?

This is a complex tool with seven parameters, deep nesting, and no output schema, so the description carries real weight. It covers the decision pipeline and cost model adequately but cuts off precisely where the output shape was being described, leaving the single most important missing piece — what the submission actually looks like — unresolved.

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 only 43%, so the description should compensate more than it does. It adds useful meaning for the network enum (Visa/Mastercard/Amex/Discover), reason-code examples, and the evidence bundle, but it does not explain the many optional evidence sub-fields (delivery confirmation, digital usage logs, prior undisputed transactions) or how their presence changes eligibility, leaving substantial nested surface undocumented in both schema and description.

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 specific verbs and a clear resource: it decides fight-vs-accept, scores win probability against network rubrics, runs CE3.0 eligibility checks, computes net recovery, and returns a processor-ready submission. An agent can tell exactly what it produces. It loses a point because the description is truncated mid-sentence, leaving the final deliverable specification incomplete.

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 phrase 'Tells a merchant whether to fight or accept a card dispute', which frames the decision context well. However, there is no explicit when-to-use versus when-not-to-use guidance, no stated prerequisites (e.g., needing the dispute already in a representment-eligible state), and no named alternative tool for cases this one does not cover.

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