Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

revclamp_lint_dispute_evidence

Lint Stripe dispute evidence payloads before submission to catch UTF-16 length overflows, unsafe block markers, lost merchant notes, wrapper capacity issues, and Visa CE 3.0 identifier gaps.

Instructions

Lints Stripe dispute evidence[access_activity_log] payloads against the 18,000 UTF-16 code unit ceiling, non-destructive RevClamp CE 3.0 block markers, merchant note preservation, 17,922/17,920-char fixed wrapper capacity threshold (SKIP_POST_PRESERVE_DRAFT), and Visa CE 3.0 two-identifier overlap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revclamp_lint_dispute_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoNoSet true to lint a sample preset fixture when evidenceLogText / accessActivityLog is omitted.
presetNoScenario preset to evaluate when custom evidenceLogText / accessActivityLog is omitted (default: 'valid_ce3_non_destructive').valid_ce3_non_destructive
hasIpMatchNoWhether the disputed charge IPv4/IPv6 address matches the historical undisputed charges.
hasDeviceMatchNoWhether the disputed charge device_id fingerprint matches the historical undisputed charges.
evidenceLogTextNoMerged or candidate Stripe dispute evidence[access_activity_log] payload evaluated against the 18,000 UTF-16 code unit ceiling and non-destructive delimiter markers.
accessActivityLogNoAlias for evidenceLogText representing Stripe dispute evidence[access_activity_log] payload.
priorMatchedCountNoNumber of prior undisputed Stripe charges (120d-365d old) with matching customer_id and IP/device fingerprint (Visa CE 3.0 requires >= 2).
priorTransactionsNoOptional historical undisputed Stripe charges (120d-365d prior) evaluated for Visa CE 3.0 two-identifier overlap.
disputedTransactionNoOptional disputed Stripe charge/transaction metadata evaluated against priorTransactions for Visa CE 3.0 qualification.
existingMerchantNotesNoExisting human AE/support notes inside evidence[access_activity_log] that must be preserved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.20.29

TDQS

B3.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 behavioral burden; it usefully discloses non-destructive block markers, merchant-note preservation, the UTF-16 ceiling, wrapper capacity handling, and Visa two-identifier overlap. It does not explicitly confirm read-only behavior, permissions, network calls, or what failure output looks like.

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 action is front-loaded and there is no filler, but the single sentence is a dense run-on packed with unexplained internal jargon and threshold combinations. Structure could be improved by separating the validation rules from the resource identification.

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 10-parameter tool with nested objects and no output schema, the description covers validation rules but omits what a lint result contains, how findings are reported, and how demo/preset/custom modes interact. It also does not clarify the all-optional invocation behavior beyond schema details.

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 100%, so all 10 parameters already have documented meanings, defaults, and constraints. The description adds rule context such as the ceiling and overlap checks, but no parameter-level guidance beyond what the schema already provides.

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?

States a specific action (lints) and target (Stripe dispute evidence[access_activity_log] payloads) and lists the exact rule domains checked. It does not name or differentiate from the closest sibling revclamp_stage_stripe_dispute_ce3, leaving an agent to infer that this is validation rather than staging.

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?

Offers no explicit when-to-use or when-not-to-use guidance, no alternatives, and no prerequisites. An agent must infer from 'lints' that this is the validation choice before staging, and the description does not explain when to use presets/demo mode versus custom payloads.

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