Loading ToolBench
MCP server for cross-chain asset transfers using Wormhole protocol
Single tool with basic schema and description. Tool name 'auto-transfer' lacks action verb prefix (should be 'transfer_assets' or similar). Description is adequate (52 chars) but generic. Schema is present with Zod validation and proper types, but lacks critical details: no explanation of what 'message' parameter does (bs58 encoding?), no output schema documented, no error handling guidance. Parameters have descriptions but lack constraints on transferAmount (no min/max beyond 0). Missing documentation of prerequisites (private keys, chain availability). No pagination, no idempotency guarantees, no recovery guidance on failure.
Automatically transfer assets between chains
Tool name lacks action verb. 'auto-transfer' should be 'transfer_assets' or 'initiate_transfer' to clearly signal the action to LLMs.
No output schema documented. Callers cannot predict response structure (txnHashes format, fields, types). LLMs cannot plan downstream operations.
'message' parameter description is incomplete. Does not explain bs58 encoding requirement or what the payload represents. LLMs will pass arbitrary strings.
No error recovery guidance. Catch block returns generic 'Failed to initiate' without actionable next steps (retry? check keys? check chain availability?).
Private keys exposed via environment variables without server-side secret injection pattern. If agent logs parameters or traces, credentials could leak.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |