Kellian

This week’s scored questions, and when the window closes

kellian_get_season_cohort

Read-onlyIdempotent

This week’s fixed set of scored questions drawn from the news, with the instant the scoring window closes. Call any of them: a call that settles is scored. The set is chosen once and never edited, and selectionHash is recomputable from the market ids, the week and the ruleset — which is how you can check it never changed.

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_get_season_cohort"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety needs no restating. The description instead adds genuinely non-obvious behavior: the set is chosen once and never edited, the close instant determines scoring, and selectionHash is recomputable from market ids, week and ruleset so immutability can be verified. That is real context beyond the structured fields.

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 sentences, front-loaded with what the cohort is before moving to the integrity mechanism. Slight redundancy between 'fixed set' and 'chosen once and never edited', and the long em-dash clause is denser than needed, but nothing is wasted.

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?

For a zero-parameter read tool with an output schema and full annotation coverage, the description covers what it returns (questions + close instant), how scoring relates to it, and why the result is trustworthy. Output format is legitimately left to the output schema.

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?

The tool takes zero parameters, so there are no parameter semantics to explain and no schema gap to compensate for. Baseline 4 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?

The description concretely identifies the resource: this week's fixed set of scored questions plus the scoring-window close instant. It is clear what an agent gets back, but it never distinguishes itself from the close sibling kellian_list_scoring_cohort (or kellian_get_current_season), so an agent has to guess which to call.

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: 'Call any of them: a call that settles is scored' hints that this is the entry point for trading the week's scored markets. There is no explicit when-to-use/when-not guidance and no mention of the sibling list_scoring_cohort, so routing between the two remains ambiguous.

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?