Skip to main content
Glama
Sign In
pathiel

pathiel

by Julian-dev28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_market

Read-only

Fetch a real-time market snapshot for one coin: mid, mark and oracle price, funding, open interest, 24h volume and max leverage in a single read-only call. Use it for any single-coin question now.

Instructions

Get one coin's market snapshot in a single call: mid, mark and oracle price, current funding and the predicted next funding per venue, open interest, 24h volume, previous-day price and max leverage. Use it for any question about one coin right now. Not for many coins at once (list_markets), price over time (get_candles) or depth and slippage (get_order_book). Read-only; needs no key or account. A HIP-3 coin (xyz:GOLD) is read from its own dex. Returns {coin, mid: {price}, context: {funding, openInterest, markPx, oraclePx, midPx, dayNtlVlm, prevDayPx}, funding_next: {venues[]}, max_leverage}; a part the venue cannot answer carries its own error while the rest still returns, and an unknown coin returns {error} with isError true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "<coin>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin: a main-dex perp by name (BTC, ETH) or a HIP-3 perp as dex:SYMBOL (xyz:GOLD, xyz:BRENTOIL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=true it adds auth posture ('needs no key or account'), routing behavior for HIP-3 coins read from their own dex, and a partial-failure contract where an unanswerable field carries its own error while the rest of the response still returns. It also documents the unknown-coin path ({error} with isError true), which annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then exclusions, then return shape — a sensible order with no filler. The field enumeration and return-shape clause are dense, but they substitute for a missing output schema, so the length is largely earned.

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?

With one parameter, no output schema and only a readOnlyHint, the description supplies the return shape, the partial-error semantics, and the error case. Nothing an agent needs to call it correctly or interpret the result is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: that a HIP-3 symbol like xyz:GOLD is resolved against its own dex rather than the main dex. That routing consequence is genuinely useful and slightly exceeds the parameter's own description.

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?

States a specific verb and resource ('Get one coin's market snapshot') and enumerates exactly what the snapshot contains (mid, mark, oracle, funding, next funding, OI, 24h volume, prev-day price, max leverage). It explicitly carves itself out from list_markets, get_candles and get_order_book, so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a positive trigger ('any question about one coin right now') and three named exclusions with the sibling that covers each case. When-to-use, when-not-to-use, and alternatives are all present in two sentences.

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