Bit2Me MCP Server

general_get_assets_config

Read-onlyIdempotent

Retrieve Bit2Me asset configurations to discover available symbols and verify trading or loan status. Filter by symbol to check if a specific crypto or fiat asset is tradeable or loanable.

Instructions

Gets asset configuration for Bit2Me. Optional symbol filter. Returns symbol, name, type (crypto/fiat), network, trading status, loan availability, and pro_trading_pairs. Use to discover symbols or verify if an asset is tradeable/loanable. [PUBLIC]

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": "general_get_assets_config"
  }
}

Input Schema

Name	Required	Description
`symbol`	No	Filter by specific asset symbol (e.g., BTC, ETH). If not provided, returns all assets.
`show_exchange`	No	Include exchange-specific properties in response
`include_testnet`	No	Include testnet/sandbox assets in response

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.1.4Jun 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: the endpoint is public, it supports an optional symbol filter, and it returns a specific set of asset fields. No contradiction with annotations.

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 sentences with no filler. It front-loads the action and resource, then gives filter behavior, return payload, and use cases. Every sentence earns its place.

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 read-only config tool with only optional parameters, the description covers purpose, return fields, public access, and use cases. Since there is no output schema, listing the returned fields is helpful. It does not mention pagination or response formatting, but that is not strongly required here.

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%, and all three parameters have clear descriptions, so the baseline is 3. The description reinforces the optional symbol filter but adds no extra meaning for show_exchange or include_testnet beyond what the schema already provides.

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 names a specific verb and resource: 'Gets asset configuration for Bit2Me.' It also lists the returned fields (symbol, name, type, network, trading status, loan availability, pro_trading_pairs) and states the intended use cases. It does not explicitly differentiate this from sibling config/getter tools, but the resource and output detail make the purpose clear.

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?

The description provides clear usage guidance: 'Use to discover symbols or verify if an asset is tradeable/loanable.' This tells an agent when to invoke the tool. It does not mention when not to use it or name alternative tools, so it falls short of a 5.

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

Deploy Server