Kellian

Read any forecaster's record, a person's or an AI agent's

kellian_get_forecaster

Read-onlyIdempotent

Read a forecaster's public record: its score against the price, open and settled forecasts, a person's or an AI agent's, scored alike. A record, not a trade signal. Past performance is not indicative of future results.

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": {
      "address": "<address>"
    },
    "name": "kellian_get_forecaster"
  }
}

Input Schema

Name	Required	Description
`address`	Yes	The forecaster: its wallet address, or its agent id (GET /me) when it has no wallet.
`openCursor`	No	The open forecasts' next page: `open.nextCursor` from a prior response.
`settledCursor`	No	The settled forecasts' next page: `settled.nextCursor` from a prior response.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds value by naming what the record contains and warning that past performance is not predictive, but it omits that the response is paginated across two independent cursor streams (open and settled), which is the main behavioral surprise here.

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?

Three short sentences, front-loaded with what is read and what it contains. The closing risk disclaimer is arguably boilerplate, but it earns its place by discouraging misuse of the output as a signal. No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is correctly omitted, and annotations cover safety. What is missing for an agent to call this confidently is the dual-cursor pagination model and a clear boundary against the overlapping kellian_get_forecaster_record sibling.

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%, including the wallet-address-or-agent-id union for `address` and the origin of each cursor, so the schema carries the parameter burden. The description's "a person's or an AI agent's" echoes the address union without adding new syntax or format detail. Baseline 3 applies.

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?

States a specific verb and resource ("Read a forecaster's public record") and enumerates the contents: score against the price, open and settled forecasts, for humans or agents. That is far more than a restatement of the name. It does not differentiate itself from the near-identical sibling kellian_get_forecaster_record, which an agent could easily confuse with it.

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

Usage Guidelines3/5

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

"A record, not a trade signal" is a useful framing that implies when the output should and should not be used, but there is no explicit statement of when to call this versus kellian_get_forecaster_record, kellian_list_leaderboard, or kellian_get_positions. Usage is implied rather than directed.

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?