Skip to main content
Glama

unstake_quote

Calculate the expected return when unstaking cryptocurrency assets to help users make informed decisions about their staked positions.

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 for unstake_quote. Validates input, checks authentication, calls the armor_client.unstake_quote API wrapper, and returns the result or error.
    @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 schema for a single unstake quote request, including wallet, input token (staked), output token (SOL), and amount.
    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 wrapping a list of UnstakeQuoteRequest instances, used as the input parameter type for the unstake_quote tool.
    class UnstakeQuoteRequestContainer(BaseModel):
        unstake_quote_requests: List[UnstakeQuoteRequest]
  • ArmorWalletAPIClient method that constructs the API payload from the input container and performs the HTTP POST to the backend /transactions/quote/ endpoint.
    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 the full burden of behavioral disclosure. It only mentions the input and output types ('UnstakeQuoteRequestContainer' and 'SwapQuoteRequestContainer'), but fails to describe what the tool actually does behaviorally—such as whether it's a read-only operation, if it has side effects, rate limits, or authentication needs. This leaves significant gaps for understanding its behavior.

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 concise with two sentences that are front-loaded, stating the purpose first and then the input/output. There's no wasted text, but it could be more structured by including usage context or parameter details.

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 the complexity (a financial quote tool with no annotations), the description is incomplete. It mentions input and output types, but lacks details on behavior, usage, or parameters. The presence of an output schema helps, but the description doesn't leverage this to provide a complete picture, leaving gaps in understanding the tool's role and operation.

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 adds minimal semantics by naming the parameter type ('UnstakeQuoteRequestContainer'), but with 0% schema description coverage and 1 parameter, it doesn't explain what this container includes or how to use it. Since there are no parameters documented in the schema, the baseline is 4, but the description fails to compensate adequately, offering only a type name without context.

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 clear verb ('Retrieve') and resource ('unstake quote'). However, it doesn't differentiate from sibling tools like 'stake_quote' or 'swap_quote' beyond the 'unstake' prefix, leaving the specific purpose somewhat vague compared to alternatives.

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?

No guidance is provided on when to use this tool versus alternatives such as 'stake_quote' or 'swap_quote'. The description lacks context about prerequisites, timing, or exclusions, offering no help for an agent to choose between similar tools.

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

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