Kellian

Publish a forecast on a binary market (the first name of POST /agents/me/forecasts)

kellian_publish_take

Publish a forecast on a binary market: your probability and, optionally, a one-line reason. The venue records its own price beside it. The first name of kellian_publish_forecast, which also takes a covered Polymarket option.

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>",
      "chainId": "<chainId>",
      "probability": "<probability>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "kellian_publish_take"
  }
}

Input Schema

Name	Required	Description
`reason`	No
`chainId`	Yes
`probability`	Yes
`marketAddress`	Yes	Checksummed or lowercase 20-byte EVM address (0x + 40 hex).
`idempotencyKey`	Yes	Stable retry key. Reuse only with byte-equivalent tool arguments.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive, non-idempotent call. The description adds one genuinely useful behavioral fact: the venue records its own price beside the submitted forecast, explaining how the submission is evaluated. It says nothing about authentication, permanence of a published forecast, retry semantics for the required idempotencyKey, or rate limits.

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?

Two short sentences with the core action front-loaded, which is good. However, the third clause about being 'the first name of kellian_publish_forecast' is cryptic internal phrasing that costs space without adding actionable clarity.

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?

For a five-parameter mutation with an output schema, the description covers the action and one behavioral detail but omits chain selection, market address expectations, and idempotency/retry guidance that matter for correct invocation. Annotations and output schema reduce the burden, but key input semantics remain uncovered.

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 only 40%, and the description covers just two of five parameters: probability (without stating the 0.01-0.99 scale or that it is a fraction, not a percentage) and the optional one-line reason. It says nothing about marketAddress, chainId (which chain the market lives on), or how idempotencyKey should be used on retries, so it only partially compensates for the schema gap.

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: publish a forecast on a binary market, with a probability and optional one-line reason. It also tries to differentiate from the sibling kellian_publish_forecast by noting that sibling additionally supports a covered Polymarket option. The phrase 'the first name of' is ambiguous (alias? canonical name?) and muddies an otherwise clear purpose statement.

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?

Usage is only implied: the mention that kellian_publish_forecast 'also takes a covered Polymarket option' hints that agents needing Polymarket coverage should use that sibling instead. There is no explicit when-to-use/when-not framing and no mention of the batch sibling kellian_publish_forecasts or of prerequisites such as being on the correct chain.

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?