nonkyc-mcp

Get ticker

get_ticker

Retrieve 24-hour ticker data for a specified NonKYC market, including last price, bid/ask, high/low, volume, and change.

Instructions

24h ticker for a NonKYC market: last price, bid/ask, high/low, volume, change.

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_ticker"
  }
}

Input Schema

Name	Required	Description	Default
`market`	No	Market as BASE_QUOTE, e.g. BTCB2_USDT, BTCB2_BTC, BTCB2_YEC	BTCB2_USDT

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the 24h window and the data points returned but says nothing about whether the operation is read-only, requires authentication, has rate limits, or whether the data is real-time or cached.

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 a single, information-dense sentence with no filler. It front-loads the scope and then lists the returned fields efficiently.

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 1-parameter tool with no output schema and no annotations, the description adequately covers the return contents by listing key fields, compensating for the missing output schema. It omits non-critical context such as authentication or rate limits, but the core information needed to call the tool is present.

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 100%; the single 'market' parameter is fully documented in the schema with format and examples. The description adds no parameter-level detail beyond what the schema already provides, so baseline 3 is appropriate.

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 the resource (24h ticker) and the scope (NonKYC market) and enumerates the returned fields, making the tool's purpose immediately clear. It does not use an explicit verb, but the tool name 'get_ticker' supplies that, and there are no siblings to distinguish from.

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?

The description states what the tool returns but gives no guidance on when to use it versus alternatives (there are none listed) or any prerequisites. Usage is only implied by the data fields listed.

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

Deploy Server

Other Tools

get_tickerB