Skip to main content
Glama
bit2me-devs

Bit2Me MCP Server

by bit2me-devs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

earn_deposit

Destructive

Deposit funds from a Simple Wallet pocket into Earn (Staking) to start earning rewards at the asset's APY. Preview the operation first, then confirm to execute.

Instructions

Deposit funds from Simple Wallet pocket to Earn (Staking). Funds will start earning rewards based on the asset's APY. Returns operation details with type: deposit. Use wallet_get_pockets to find your pocket ID and earn_get_positions to see available Earn strategies. Operation status ENUM: pending (operation in progress), completed (successfully finished), failed (operation failed or was cancelled). [PRIVATE] First call without confirm=true returns a preview; set confirm=true only after the user agrees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jwtNoOptional session token for authentication. API keys are recommended for most use cases.
amountYesAmount to deposit into Earn (as string for decimal precision)
symbolYesCryptocurrency symbol (e.g., BTC, ETH)
confirmNoMust be true to execute. Ask the user first, then call again with confirm=true. Prevents accidental one-shot mutations by the LLM.
pocket_idYesSource pocket UUID from Simple Wallet
idempotency_keyNoStable key for this logical action (UUID recommended). Reuse the same value when retrying after a timeout so Bit2Me does not execute twice. Auto-generated if omitted.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv4.5.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to execute. Ask the user first, then call again with confirm=true. Prevents accidental one-shot mutations by the LLM.",
+  "type": "boolean"
+}
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Stable key for this logical action (UUID recommended). Reuse the same value when retrying after a timeout so Bit2Me does not execute twice. Auto-generated if omitted.",
+  "type": "string"
+}
  2. First observedv4.1.4

TDQS

A4.4/5.0
Behavior5/5

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

Goes beyond annotations: reveals the preview-then-confirm two-call pattern, enumerates operation statuses, and notes that rewards start accruing. For a mutating tool this is substantial behavioral context beyond readOnly/destructive hints.

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

Conciseness5/5

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

Four dense sentences with no fluff: action, consequence, return shape, prerequisite lookups, status enum, and confirmation protocol are all front-loaded and necessary.

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

Completeness4/5

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

Complete for a mutating tool: describes prerequisites, preview/confirm, status values, and helper tools. Without an output schema, it could spell out more of the operation-details structure, but the status enum and type: deposit cover the main return expectations.

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 schema already documents all six parameters. The description adds useful context for pocket_id and confirm, but does not need to repeat parameter definitions.

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

Purpose5/5

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

States a precise action: transfer funds from Simple Wallet pocket to Earn/Staking. It distinguishes itself from earn_withdraw by direction and specifies the return type (operation details with type: deposit).

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

Usage Guidelines4/5

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

Tells the agent to use wallet_get_pockets to resolve pocket_id and earn_get_positions to find available strategies. It also explains the preview/confirm protocol. It does not explicitly contrast with earn_withdraw, but the deposit/withdraw direction is clear from the description.

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/bit2me-devs/bit2me-mcp'

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