MCP server for Visa Intelligent Commerce (VIC) API integration, providing tools for payment instruction management, credential handling, and transaction operations
Critical gaps across all dimensions. Tool definitions lack proper schemas, most parameters are documented in descriptions only, not in formal JSON Schema with type constraints. Descriptions are minimal (10-50 chars), well below the 50-200 char baseline for LLM-optimized tools. No enums for constrained inputs (e.g., currency codes, event IDs). Output schemas are undocumented. Error handling is absent, no recovery guidance, no categorization of retryable vs. fatal errors. Security concerns: enrollCard exposes sensitive card data (number, expiry) as parameters; no mention of secret injection or permission gates. Tool composition issues: callTool is a meta-tool that duplicates listTools functionality; createInstruction, updateInstruction, cancelInstruction lack idempotency guarantees or confirmation patterns for destructive operations. No pagination support for list operations. Naming is acceptable (verb-noun pattern) but descriptions fail to explain WHEN to use each tool or what distinguishes similar operations (e.g., updateInstruction vs. cancelInstruction).
Calls a tool directly through the MCP client with specified arguments
Cancels an existing purchase instruction
Confirms transaction events in the Visa VIC system
Creates a new purchase instruction in the Visa VIC system
Enrolls a card in the Visa VIC system
Lists all available tools from the MCP server
Retrieves payment credentials from the Visa VIC system
Updates an existing purchase instruction
No formal JSON Schema with type constraints. Parameters documented in descriptions only; missing enum constraints for currency, event IDs, and other constrained inputs. Violates pattern:constrained-input.
Descriptions are 10-50 characters, far below 50-200 char baseline. Lack WHEN/WHY guidance. LLMs cannot distinguish updateInstruction from cancelInstruction or know when to call retrieveCredentials vs. confirmTransactionEvents.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields (e.g., instructionId from createInstruction response). Violates pattern:tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
Security: enrollCard exposes cardNumber and expiryDate as parameters. Violates pattern:secret-injection, credentials must never appear in tool parameters; use server-side injection. Card data will be logged in agent traces.
No error handling guidance. Tools lack recovery hints, error categorization (retryable vs. fatal), or actionable error messages. Violates pattern:recovery-guide and pattern:error-classification.