Sera MCP Server

Official

by sera-cx

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

get_wallet_info

Fetch the configured wallet's address, balance, and chain for your Sera account.

Instructions

Get information about the configured wallet (address, balance, chain). Requires WALLET_PRIVATE_KEY to be set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_wallet_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are present, so the description carries the burden. It mentions the private key requirement and specifies the returned fields, but does not disclose error handling, read-only nature, or side effects. This is basic but not rich context.

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?

The description is two short sentences, front-loaded with the core purpose, and includes the key requirement without any wasted words.

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?

For a simple getter, the description covers the output fields (address, balance, chain) and the setting requirement. However, it omits failure modes or differentiation from the sibling get_wallet_balances, so it's slightly incomplete.

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 input schema has zero parameters, and schema description coverage is trivially 100%. Per guidelines, a 0-param tool receives a baseline of 4 since there are no parameters to explain.

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?

Description clearly states 'Get information about the configured wallet (address, balance, chain)' — a specific verb and resource. It distinguishes from sibling get_wallet_balances by covering broader wallet info beyond just balances.

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

Usage Guidelines3/5

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

Provides a clear prerequisite ('Requires WALLET_PRIVATE_KEY to be set') but does not explicitly discuss when to use this tool versus alternatives like get_wallet_balances or get_exchange_balance. Usage is implied by the tool's purpose but no exclusionary guidance is given.

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