Skip to main content
Glama
bit-oasis

BitOasis MCP Server

Official
by bit-oasis

get_markets

Retrieve a list of all tokens and trading pairs on BitOasis, including each token's trading, deposit, and withdrawal status.

Instructions

List all available tokens and trading pairs on BitOasis.

Returns each token's symbol, name, and whether trading/deposits/withdrawals are enabled, along with available trading pairs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description explains the return fields (symbol, name, status, pairs), which is transparent enough for a read-only list operation. No annotations exist, but it doesn't cover rate limits or other traits, though not critical here.

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?

Extremely concise: two sentences, front-loaded with the action, then details the return fields. No wasted words.

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

Completeness5/5

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

Given no parameters and an output schema, the description fully covers what the tool does and returns. No missing aspects.

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?

No parameters exist, so the description adds no parameter value. Baseline score of 4 is appropriate as there is no need for additional parameter info.

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 clearly states the tool lists all tokens and trading pairs on BitOasis, with specific verbs and resource. It distinguishes from siblings like get_ticker or get_order_book, which focus on specific items.

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?

No explicit guidance on when to use vs alternatives. While it's clear the tool lists all markets, there is no mention of exclusions or comparisons to similar tools like get_ticker.

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/bit-oasis/bitoasis-mcp'

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