show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Bity
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds no extra behavioral disclosure. It doesn't contradict 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?
A single, front-loaded sentence with no filler. Every word is necessary and earns its place.
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?
For a zero-parameter, read-only tool without output schema, the description fully explains what the tool does. It is complete and sufficient.
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, and schema description coverage is 100%. The description adds no parameter info, but baseline for 0 params is 4, and nothing is needed beyond what the schema provides.
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 it shows MCP platform and adapter versions. It uses a specific verb ('Show') and resource ('MCP platform and adapter versions'), distinguishing it from sibling tools that handle authentication, market data, etc.
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?
No explicit when-to-use or alternatives, but given the tool's simplicity, the purpose implicitly guides usage. It provides clear context for a version check, lacking only exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.1/5.0
Disambiguation5/5
Each Bity tool targets a distinct resource (balance, orders, ticker, trades, orderbook) and the platform tools (authenticate, connect, marketplace, etc.) serve clearly separate functions. There is no real overlap or ambiguity between any of the tools.
Naming Consistency2/5
The Bity tools use a 'bity_' prefix, but the naming pattern is inconsistent: bity_get_balance uses a verb, while bity_orderbook and bity_ticker are just nouns. The non-Bity tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) follow no common pattern and break the verb_noun convention.
Tool Count3/5
At 14 tools, the count is within a reasonable range, but the server mixes a focused Bity integration with generic platform tools (marketplace, report_bug, etc.), making the scope feel inflated. A dedicated Bity server would not need the platform-layer tools, so the count is slightly high for the apparent purpose.
Completeness2/5
The Bity toolset covers read-only operations: balance, orders, ticker, trades, orderbook. There is no tool to create, cancel, or modify orders, which is a fundamental omission for a trading exchange. The server cannot execute any trades, so it fails to provide a complete lifecycle for its core domain.