Kellian

Get orderbook depth for a market

kellian_get_orderbook

Read-onlyIdempotent

Get orderbook depth for a market

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": {
      "marketAddress": "<marketAddress>"
    },
    "name": "kellian_get_orderbook"
  }
}

Input Schema

Name	Required	Description	Default
`side`	No	Outcome side: 0=outcome 1, 1=outcome 2. Required for executable_for_caller; optional for public aggregate depth.
`view`	No	public (default) includes all makers. executable_for_caller excludes only the wallet bound to the authenticated MCP session.	public
`depth`	No	Price levels per side (default: 20)
`chainId`	No	Chain id for the market address. Required when the same market address exists on multiple chains.
`marketAddress`	Yes	Orderbook market contract address

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without the description. The description adds nothing behavioral beyond that - notably it never mentions the meaningful public vs executable_for_caller view distinction, which changes what data is returned to the caller.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but it is under-specified rather than concise - it is a verbatim restatement of the title with no additional content for an agent to act on.

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?

For a 5-parameter tool with an enum view mode, a conditional chainId, and caller-scoped filtering semantics, the description is far too thin. The output schema and annotations cover return values and safety, but the description should explain the public vs authenticated view tradeoff and the multi-chain caveat.

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%, so the schema already documents depth, view, side, chainId, and marketAddress. The description adds no parameter meaning at all, so the baseline 3 applies for a schema that does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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?

There is no when-to-use guidance at all: nothing says when this single-market orderbook call should be preferred over kellian_batch_get_orderbooks for multiple markets or kellian_get_market_depth for aggregated depth. Usage must be inferred entirely from the name and schema.

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

All Kellian tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?