Skip to main content
Glama
bit-oasis

BitOasis MCP Server

Official
by bit-oasis

get_ticker

Retrieve current market price and ticker data for a specified cryptocurrency trading pair on BitOasis. Use this to obtain real-time price information for pairs like BTC-AED or ETH-AED.

Instructions

Get current price/ticker information for a trading pair.

Args: pair: Trading pair, e.g. "BTC-AED", "ETH-AED", "SOL-AED".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose that this is a read-only operation, nor any behavioral traits such as rate limits or data freshness. The minimal description adds little beyond the action itself.

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?

Exceptionally concise with no wasted words. The purpose is stated in the first sentence, followed by a single parameter description. Ideal length for a simple tool.

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?

Despite having an output schema, the description lacks completeness. It does not describe what the ticker information includes (e.g., bid, ask, last price) or how it differs from related tools. The minimal information may leave an agent uncertain about the tool's scope.

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 0%, so the description partially compensates by explaining the pair parameter with examples. However, it does not specify accepted formats or constraints beyond the examples, leaving ambiguity.

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 clearly states it retrieves current price/ticker information for a trading pair, using a specific verb and resource. However, it does not differentiate from sibling tools like get_order_book or get_trades, which could also involve price data.

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 on when to use this tool over alternatives; no mention of prerequisites or context. The description simply states what it does without indicating when it is appropriate.

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