Sera MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

prepare_deposit

Creates a deposit transaction to move tokens from your wallet to the exchange balance. Provide token address, amount, and wallet address.

Instructions

Prepare a deposit transaction to move funds from wallet to exchange balance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token_address": "<token_address>",
      "amount": "<amount>",
      "owner_address": "<owner_address>"
    },
    "name": "prepare_deposit"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	Amount to deposit (human-readable)
`owner_address`	Yes	Wallet address
`token_address`	Yes	Token to deposit

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden, but it only states intent. It does not disclose whether 'prepare' actually moves funds, returns a signed transaction, or has side effects, auth requirements, or return value.

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?

A single, front-loaded sentence with no filler or repetition. It states the action and purpose efficiently.

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?

The description is too thin for a tool that prepares an action. It lacks output/return information, does not clarify whether execution happens, and gives no workflow context linking it to execute_deposit.

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 coverage is 100%, so the schema already documents each parameter. The description adds the wallet-to-exchange context, helping identify owner_address as the source, but does not meaningfully extend token/amount semantics.

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?

The description uses a specific verb ('prepare') and resource ('deposit transaction') plus source/destination ('wallet to exchange balance'). This clearly distinguishes it from siblings like execute_deposit and prepare_withdraw.

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 about when to use this tool versus alternatives like execute_deposit or prepare_withdraw. It does not state prerequisites, exclusions, or the two-step workflow context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.