Loading ToolBench
MCP server for unified global payment acquiring with risk orchestration capabilities
Critical failures across all dimensions. The single tool 'execute_skill_action' has a minimal description (58 chars, below the 10-1024 baseline), lacks output schema documentation, and the tool definition is inferred from client code rather than explicitly registered in the MCP server. The mcp_server.py file contains only a hardcoded JSON response with no actual tool registration, schema validation, or parameter handling. No error handling, no input validation, no security controls. The server does not implement the MCP protocol, it merely prints a static JSON string and exits.
Execute unified global payment acquiring and risk orchestration skill action
Tool definition not explicitly registered in MCP server. Tool exists only in client.py; mcp_server.py contains no tool registration, schema, or handler. Tool definitions must be visible in the server code.
No output schema documented. Tool description and client code do not specify what fields the response contains. LLMs cannot plan downstream calls or extract required data.
Tool description is 58 characters ('Execute unified global payment acquiring and risk orchestration skill action'). Below the 10-1024 baseline and lacks WHAT, WHEN, and WHY context. Does not explain when to use this vs other payment tools or what the response contains.
No error handling or recovery guidance. No validation of inputs (e.g., is transaction_amount_eur > 0? Is payment_method one of a known set?). No error responses documented. Agents cannot self-correct on invalid input.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 22 | 2026-07-28+ | v2 |
MCP server does not implement the protocol. mcp_server.py prints a static JSON string and exits. No request/response loop, no tool invocation handler, no parameter parsing. This is not a functional MCP server.