Skip to main content
Glama
armorwallet
by armorwallet

stake_transaction

Execute stake transactions on Armor Crypto MCP by processing StakeTransactionRequestContainer inputs and generating SwapTransactionRequestContainer outputs for blockchain operations.

Instructions

Execute a stake transaction.

Expects a StakeTransactionRequestContainer, returns a SwapTransactionRequestContainer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stake_transaction_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
swap_transaction_requestsYes

Implementation Reference

  • The primary handler and registration (@mcp.tool()) for the 'stake_transaction' tool. Proxies requests to the ArmorWalletAPIClient.stake_transaction method, handling authentication check and errors.
    @mcp.tool()
    async def stake_transaction(stake_transaction_requests: StakeTransactionRequestContainer) -> SwapTransactionRequestContainer:
        """
        Execute a stake transaction.
        
        Expects a StakeTransactionRequestContainer, returns a SwapTransactionRequestContainer.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: SwapTransactionRequestContainer = await armor_client.stake_transaction(stake_transaction_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic model defining the input schema for a single stake transaction request, containing the transaction_id from a prior stake quote.
    class StakeTransactionRequest(BaseModel):
        transaction_id: str = Field(description="unique id of the generated stake quote")
  • Pydantic container model wrapping a list of StakeTransactionRequest for batch input to the stake_transaction tool.
    class StakeTransactionRequestContainer(BaseModel):
        stake_transaction_requests: List[StakeTransactionRequest]
  • Helper method in ArmorWalletAPIClient that performs the actual API call to execute stake transactions via the /transactions/swap/ endpoint.
    async def stake_transaction(self, data: StakeTransactionRequestContainer) -> StakeTransactionRequestContainer:
        """Execute the stake transactions."""
        payload = data.model_dump(exclude_none=True)['stake_transaction_requests']
        return await self._api_call("POST", "transactions/swap/", payload)
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states it 'executes' a transaction and mentions input/output container types, but doesn't disclose critical behavioral traits: whether this is a read-only or destructive operation, what permissions are required, whether it's irreversible, what happens on failure, rate limits, or side effects. 'Execute' implies a write/mutation, but this isn't explicitly confirmed.

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 appropriately concise with only two sentences. It's front-loaded with the core action ('Execute a stake transaction') and follows with input/output information. There's no unnecessary verbiage, though the brevity comes at the cost of completeness.

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?

Given the complexity of a financial transaction tool with no annotations and 0% schema description coverage, the description is insufficient. While an output schema exists (reducing need to explain return values), the description doesn't address critical context: what 'stake' means, relationship to sibling tools like 'stake_quote', safety considerations for a transaction execution, or parameter semantics. For a tool that likely modifies financial state, this is inadequate.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate. The description mentions 'Expects a StakeTransactionRequestContainer' but provides no semantic information about what this container represents, what 'stake_transaction_requests' should contain, or what 'transaction_id' refers to. It doesn't explain the relationship between the quote and transaction or what values are expected. No parameter guidance beyond naming the input type.

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

Purpose2/5

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

The description states 'Execute a stake transaction' which is a tautology of the tool name 'stake_transaction'. It doesn't specify what 'stake' means in this context (staking cryptocurrency, tokens, etc.) or what resource is being acted upon. While it mentions input/output containers, this doesn't clarify the actual purpose beyond the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives. There are sibling tools like 'stake_quote', 'unstake_transaction', and 'swap_transaction', but the description doesn't explain the relationship or when this specific tool should be selected. No prerequisites, conditions, or exclusions are mentioned.

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