Skip to main content
Glama
armorwallet
by armorwallet

unstake_quote

Generate an unstake quote for liquid staking derivative tokens. Input wallet details and token amounts to receive a swap quote response for unstaking transactions.

Instructions

Retrieve an unstake quote.

Expects a UnstakeQuoteRequestContainer, returns a SwapQuoteRequestContainer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unstake_quote_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
swap_quote_requestsYes

Implementation Reference

  • MCP tool handler function for 'unstake_quote'. Registers the tool via @mcp.tool() decorator and implements the logic by calling armor_client.unstake_quote with error handling for authentication and exceptions.
    @mcp.tool()
    async def unstake_quote(unstake_quote_requests: UnstakeQuoteRequestContainer) -> SwapQuoteRequestContainer:
        """
        Retrieve an unstake quote.
    
        Expects a UnstakeQuoteRequestContainer, returns a SwapQuoteRequestContainer.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: UnstakeQuoteRequestContainer = await armor_client.unstake_quote(unstake_quote_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic BaseModel defining the structure for a single unstake quote request, used within UnstakeQuoteRequestContainer.
    class UnstakeQuoteRequest(BaseModel):
        from_wallet: str = Field(description="The name of the wallet that input_token is in.")
        input_token: str = Field(description="the public mint address of the input liquid staking derivative token to unstake.") # "jupSoLaHXQiZZTSfEWMTRRgpnyFm8f6sZdosWBjx93v"
        output_token: str = "So11111111111111111111111111111111111111112"
        input_amount: float = Field(description="input amount to swap")
  • Pydantic container model holding a list of UnstakeQuoteRequest instances, serving as the input type annotation for the unstake_quote tool handler.
    class UnstakeQuoteRequestContainer(BaseModel):
        unstake_quote_requests: List[UnstakeQuoteRequest]
  • Supporting method in ArmorWalletAPIClient that serializes the request container to payload and invokes the API POST /transactions/quote/ endpoint to fetch the unstake quote.
    async def unstake_quote(self, data: UnstakeQuoteRequestContainer) -> UnstakeQuoteRequestContainer:
        """Obtain an unstake quote."""
        payload = data.model_dump(exclude_none=True)['unstake_quote_requests']
        return await self._api_call("POST", "transactions/quote/", payload)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool expects and returns at a type level ('UnstakeQuoteRequestContainer' to 'SwapQuoteRequestContainer'), but doesn't explain what unstaking entails, whether this is a read-only quote operation versus an actual transaction, what permissions are needed, or any rate limits. For a financial tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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 extremely concise with just two sentences that directly state the purpose and input/output types. There's no wasted verbiage, and it's front-loaded with the core action. However, it's arguably too terse for a financial operation where more context would be helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a financial quote tool with no annotations but with a detailed input schema and output schema (implied by 'returns a SwapQuoteRequestContainer'), the description provides the minimum viable information about what the tool does. However, it lacks crucial context about what unstaking means in this system, how quotes work, and relationship to actual transaction tools. The presence of output schema reduces the need to describe return values, but overall completeness is marginal.

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?

The description mentions the parameter type ('UnstakeQuoteRequestContainer') but provides no semantic details about what this container represents or what fields it should contain. With 0% schema description coverage, the schema itself documents the structure well (wallet, amount, token details), but the description adds almost no value beyond naming the parameter type. The baseline is appropriate given the schema does the documentation work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Retrieve[s] an unstake quote' which provides a basic verb+resource combination, but it's vague about what an 'unstake quote' actually represents. It doesn't distinguish this from sibling tools like 'stake_quote' or 'swap_quote' beyond the name difference, nor does it explain the financial context of unstaking.

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. There's no mention of prerequisites, when unstaking is appropriate, or how this differs from related tools like 'unstake_transaction' or 'swap_quote' in the sibling list. The agent receives no contextual decision-making help.

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

Related 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/armorwallet/armor-crypto-mcp'

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