Kellian

Turn an order in PM terms (market reference, outcome, PM or shares, price in percent) into the exact place-order arguments

kellian_plan_pm_order

Read-onlyIdempotent

Turn an order in PM terms (market reference, outcome label, PM budget or shares, price in percent) into the exact kellian_place_limit_order arguments, with an estimate and the market minimums. Read-only; refuses in plain words.

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": {
      "marketReference": "<marketReference>",
      "outcome": "<outcome>",
      "action": "<action>",
      "orderType": "<orderType>"
    },
    "name": "kellian_plan_pm_order"
  }
}

Input Schema

Name	Required	Description
`action`	Yes
`shares`	No	Sell or limit order: the number of shares.
`outcome`	Yes	The outcome label, exactly as the market shows it.
`budgetPm`	No	Market buy only: the PM to spend, fee included.
`expiresAt`	No	Limit order only, optional: when it stops resting. Without it, the order rests until trading ends.
`orderType`	Yes
`marketReference`	Yes	A market reference from discovery, such as "mkt_…".
`limitPricePercent`	No	Limit order only: the price per share in percent, on the market’s price steps.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4/5.0

Behavior4/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. Beyond that, the description adds real behavioral context: it refuses invalid input 'in plain words' rather than erroring opaquely, and it returns an estimate plus the market minimums, signaling that planning can fail on minimums even with valid arguments.

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?

A single dense sentence with the transformation front-loaded, followed by the output summary and the refusal note. No filler or repetition; every clause carries information.

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

Completeness4/5

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

With 8 parameters and an output schema, the description covers what the tool produces (arguments, estimate, minimums) and that it is non-executing and can refuse. It omits prerequisites such as needing an operable market reference from discovery and the pairing rules between orderType and shares/budgetPm, though those are largely carried by the schema.

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 75%, so the schema already documents most parameters, and the description's mention of market reference, outcome label, PM budget or shares, and price in percent largely restates them. It does add the useful framing that price is 'in percent,' but silent on action, orderType, and expiresAt beyond what the schema provides.

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 transformation: 'Turn an order in PM terms ... into the exact kellian_place_limit_order arguments,' naming the target sibling tool explicitly. It also enumerates the input domain (market reference, outcome label, PM budget or shares, price in percent) so an agent can distinguish it from kellian_place_limit_order or kellian_estimate_market_order without opening the schema.

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: by producing 'the exact kellian_place_limit_order arguments,' it suggests this is a pre-flight step before placing an order, but it never states when to choose it over kellian_place_limit_order, kellian_prepare_trade, kellian_batch_prepare_orders, or kellian_estimate_market_order. No explicit when-not or prerequisite conditions are given.

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?