Skip to main content
Glama
armorwallet
by armorwallet

get_stake_balances

Retrieve staked SOL (jupSOL) balances using the MCP server for blockchain integration, simplifying crypto asset tracking and management.

Instructions

Get the balance of staked SOL (jupSOL).

Returns a StakeBalanceResponse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
total_stake_amountYesTotal stake balance in jupSol
total_stake_amount_in_usdYesTotal stake balance in USD

Implementation Reference

  • MCP tool handler function for 'get_stake_balances'. Registers the tool via @mcp.tool() decorator and delegates to armor_client.get_stake_balances(), handling errors.
    @mcp.tool()
    async def get_stake_balances() -> StakeBalanceResponse:
        """
        Get the balance of staked SOL (jupSOL).
        
        Returns a StakeBalanceResponse.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: StakeBalanceResponse = await armor_client.get_stake_balances()
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Core implementation in ArmorWalletAPIClient that performs the HTTP GET request to retrieve stake balances from the API endpoint.
    async def get_stake_balances(self) -> StakeBalanceResponse:
        """Get the stake balances."""
        return await self._api_call("GET", "frontend/wallets/stake/balance/")
  • Pydantic model defining the output schema for stake balances: total_stake_amount and total_stake_amount_in_usd.
    class StakeBalanceResponse(BaseModel):
        total_stake_amount: float = Field(description="Total stake balance in jupSol")
        total_stake_amount_in_usd: float = Field(description="Total stake balance in USD")
  • The @mcp.tool() decorator registers this function as the MCP tool named 'get_stake_balances'.
    @mcp.tool()
    async def get_stake_balances() -> StakeBalanceResponse:
        """
        Get the balance of staked SOL (jupSOL).
        
        Returns a StakeBalanceResponse.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: StakeBalanceResponse = await armor_client.get_stake_balances()
            return result
        except Exception as e:
            return [{"error": str(e)}]
Behavior2/5

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

With no annotations, the description carries full burden but only states it returns a StakeBalanceResponse without detailing behavior like permissions, rate limits, or data freshness. It lacks critical context for a read operation in a financial/staking context.

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 brief and front-loaded with the core purpose, using only two sentences. However, the second sentence about the return type could be integrated more smoothly, slightly affecting structure.

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 tool's simplicity (0 params, output schema exists), the description is minimally adequate. However, it lacks context on staking specifics or integration with sibling tools, making it incomplete for optimal agent use despite the structured support.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema coverage, so no parameter info is needed. The description doesn't add parameter details, but this is acceptable as the schema fully covers the absence of inputs, aligning with baseline expectations.

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 action ('Get') and resource ('balance of staked SOL (jupSOL)'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_wallet_token_balance' or 'get_all_wallets', which also retrieve balance information, so it misses full sibling distinction.

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. For example, it doesn't specify if this is for staked balances only, as opposed to other balance-checking tools, leaving usage context unclear.

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