Skip to main content
Glama
BlueprintAIx

@blueprintaix/blueprint-mcp

Official
by BlueprintAIx

Withdraw asset from a solana vault

solana-withdraw-from-vault

Withdraw a specified USD amount from a Solana/SVM vault to your wallet. Provide vault ID, withdrawal amount, and recipient address.

Instructions

Withdraw certain USD-equivalent asset from a vault on Solana/SVM-chain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultIdYesSolana/SVM Vault ID to withdraw from
amountUsdYesWithdrawal amount (*USD*)
requestIdYesSYSTEM PARAMETER
percentageNoPercentage of holdings to withdraw (0-100). Acts as a additional hint along with the amountUsd & amountNative.
amountNativeNoWithdrawal amount in the lowest denomination of the share token
solanaWalletAddressYesUser's Solana/SVM wallet address to receive the withdrawn funds
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are empty, so the description carries the full burden, but it only restates the basic action with no disclosure of side effects, reversibility, permissions, or post-conditions. It does not go beyond the verb 'withdraw' to explain behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with the verb front-loaded and no redundancy. The word 'certain' adds little value and the phrasing is slightly awkward, but it is still appropriately concise.

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?

With 6 parameters, no output schema, and empty annotations, the description provides only a minimal statement. It fails to explain the interplay among amountUsd, amountNative, and percentage, which is critical for correct invocation.

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 the baseline is 3. The description mentions 'USD-equivalent asset', which loosely relates to amountUsd, but adds no new semantics beyond what the schema already provides for each parameter.

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?

The description clearly states the verb 'Withdraw' and the resource 'vault on Solana/SVM-chain', distinguishing it from EVM or Sui siblings. However, the phrase 'certain USD-equivalent asset' is somewhat vague about which asset, so it's not perfect.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The chain name implies usage for Solana, but no explicit when-to-use or comparison to sibling tools is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BlueprintAIx/blueprint-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server