Loading ToolBench
Stellar wallet and treasury management MCP server. Provides tools for Stellar transactions, Blend protocol interactions, policy-based spending controls, and agent management.
Nebula MCP has 28 tools with basic naming and descriptions, but significant quality gaps. All tools have descriptions (10-100 chars, mostly 40-80 chars), which is positive. However, parameter schemas are minimal or absent for many tools. Tools like 'ping', 'help', 'get_address', 'check_balance', 'request_funding', 'optimize_treasury', 'set_liquidity_threshold', 'get_policy_status', 'await_confirmation', 'get_my_reputation', 'trustline_status' have empty input schemas ({}), meaning no parameters are documented. For tools with parameters (transfer, swap, blend_deposit, etc.), descriptions are present but terse (15-40 chars), and no enum constraints, ranges, or format specifications are visible. Error handling is not evident in the tool definitions. Output schemas are not documented. Naming is verb-first and generally clear (get_, check_, transfer, swap, blend_), but some names are ambiguous: 'optimize_treasury' and 'set_liquidity_threshold' both modify state but lack confirmation/dry-run patterns. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present despite clear risk classifications (READ_ONLY vs WRITE). The server lacks composition guidance, no documentation of which tools chain together or what IDs/references are returned.
Wait for a pending confirmation to be approved or rejected
Deposit XLM or USDC into Blend protocol for yield
Withdraw XLM or USDC from Blend protocol
Check Stellar account balance for XLM and other assets
Get the Stellar address for the authenticated principal
Get reputation score for the authenticated identity
11 tools have empty input schemas ({}), providing zero parameter documentation. This violates the pattern:tool requirement that every parameter must have a description and type.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications. WRITE tools like 'transfer', 'swap', 'blend_deposit' should be marked destructiveHint=true to signal irreversibility to agents.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
Get the current spending policy and limits
Get a quote for swapping between XLM and USDC
List available tools and their descriptions
Close an MPP session
Fetch data within an MPP session
Open a Micropayment Protocol session
Make a payment within an MPP session
Get the status of an MPP session
Automatically optimize treasury allocation between liquid and Blend-deposited assets
Health check / connectivity test
Register an identity on the Stellar network
Request funding to the account wallet
Set the minimum liquidity threshold for treasury management
Get a report of spending activity and policy compliance
Execute a swap between XLM and USDC with policy-based confirmation
Transfer XLM to a destination address with policy-based confirmation
Borrow against a trustline
Establish a trustline for an asset
Repay a trustline loan
Get the status of a trustline
Fetch data using X402 protocol (pay-per-request)
Make a payment using X402 protocol
Parameter descriptions are terse (15-40 chars) and lack actionable constraints. E.g., 'Amount in XLM to transfer' does not specify range, precision, or minimum. 'Asset to swap from' does not explain what happens if the asset is not supported.
No output schemas documented. Tools like 'transfer', 'swap', 'get_swap_quote' do not specify what fields are returned, making it impossible for agents to plan downstream calls or extract required IDs.
No error handling guidance. Tools that perform financial operations (transfer, swap, x402_pay) do not document what errors can occur, whether they are retryable, or what the agent should do next.