Skip to main content
Glama
Sign In

Kellian

by app.kellian
OverviewDiscussionsAdmin

Read this wallet’s dead-man session and its recent venue lapse-cancels

kellian_orderbook_heartbeat_status
Read-onlyIdempotent

Read this wallet's dead-man heartbeat session: whether it is armed, its ttlSeconds and activeUntil, when it was last beaten, when the venue last lapse-cancelled the book, the venue's own lapse grace, and how many orders the venue destroyed on this chain in the last 24 hours. Read-only — it never arms, renews, or disarms anything.

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": "kellian_orderbook_heartbeat_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoCompiled protocol release chain ID (Base 8453).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real content: the concrete state fields returned, the 24-hour destruction window scoped 'on this chain', and an explicit no-side-effects guarantee. It does not mention auth/scoping requirements (e.g., whose wallet is 'this wallet'), which is a minor gap.

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?

One dense sentence that front-loads the core purpose and then lists the returned facts, followed by a short safety clause. No filler, no repetition of the title or schema.

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?

The tool is a simple one-parameter read with an output schema, and the description still pre-summarizes the returned fields so the agent can decide relevance before calling. Nothing needed to invoke it correctly is missing.

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 coverage is 100% and the single chainId parameter is documented in-schema, so baseline 3 applies. The phrase 'on this chain' hints that the daily destruction count is chain-scoped but adds no syntax or default detail beyond the schema.

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 ('Read') and a specific resource ('this wallet's dead-man heartbeat session'), then enumerates exactly what is returned: armed status, ttlSeconds, activeUntil, last beat, last venue lapse-cancel, venue grace, and 24h destroyed-order count. The closing clause ('never arms, renews, or disarms anything') cleanly separates it from the mutating sibling kellian_orderbook_heartbeat.

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?

The read-only disclaimer makes the when-not case explicit: this tool observes the heartbeat, it does not arm or renew it. However, it never names kellian_orderbook_heartbeat as the tool to use for the mutating actions, leaving the routing inference to the agent.

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

All Kellian toolsInspect
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