Skip to main content
Glama
stripe-chargeback-dispute-evidence-automator-mcp

stripe-chargeback-dispute-evidence-automator-mcp

check_visa_ce30_eligibility

Evaluate disputed transactions against historical settlements to determine Visa CE 3.0 eligibility, validate the 120–365 day window and matching elements, and return a win-probability score.

Instructions

Evaluates a disputed transaction against merchant historical settlement records under Visa Compelling Evidence 3.0 (CE 3.0). Validates the 120-365 day window, undisputed status, and checks 2+ matching elements (IP, device fingerprint, billing address hash, customer ID, email). Returns eligibility verdict, matched elements, rules breakdown, and win probability score (0-100).

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": {
      "disputedCharge": "<disputedCharge>"
    },
    "name": "check_visa_ce30_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
disputedChargeYesThe disputed charge object with id, created date, and matching indicators (ipAddress, deviceId, billingAddress, customerEmail, userAccountId).
priorTransactionsNoArray of historical settled transactions associated with the customer payment credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the 120-365 day window rule, the undisputed-status precondition, the 2+ matching-element threshold, and the returned verdict, matched elements, rules breakdown, and 0-100 win probability. It stops short of stating that the tool is a side-effect-free computation and says nothing about failure modes when prior transactions are absent.

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?

Three tightly packed sentences: what it does, the rules it enforces, and what it returns. The most important information (the CE 3.0 evaluation) leads, and no sentence is filler.

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 two-parameter tool with nested objects and no output schema, the description covers inputs of interest, the eligibility rules, and the shape of the response, which is enough to call it correctly. It could go further on how many priorTransactions are needed and what an ineligible verdict looks like.

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 schema already documents both parameters, but the description adds meaning: it names the five matching elements (IP, device fingerprint, billing address hash, customer ID, email) that map onto ipAddress, deviceId, billingAddress, userAccountId, and customerEmail. It also ties the 120-365 day window to the created dates and the undisputed requirement to the disputed flag, which the schema does not explain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "Evaluates a disputed transaction against merchant historical settlement records under Visa Compelling Evidence 3.0 (CE 3.0)." The Visa CE 3.0 framing plus the eligibility-verdict output clearly separates it from compile_stripe_dispute_evidence (evidence assembly) and audit_merchant_chargeback_ratio (portfolio auditing).

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?

The eligibility-checking context implies when to reach for it (a chargeback where the merchant holds prior settled transactions), but it never names the sibling tools or states when NOT to use it, e.g. when no prior transaction history exists the check cannot succeed. Usage is inferable rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.