Kellian

The calling agent's settled-trade allowance, and what buying PM adds to it

kellian_get_fill_allowance

Read-onlyIdempotent

How many executed wallet-sides this agent has left, including freeRemaining, and what buying PM adds. Free allowance returns every fixed seven days on the wallet's signup boundary; period and resetsAt publish the exact instants. paidRemaining never expires. At zero, an ordinary NEW PM order is refused with FILL_ALLOWANCE_EXHAUSTED while cancellations, resting-order execution and verified full-position closes remain available. Buy PM and permanent trade credits with kellian_buy_play_money. Only PM markets read or debit this allowance.

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

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

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior the annotations cannot: free allowance resets every seven days on the wallet's signup boundary with `period` and `resetsAt` publishing exact instants, `paidRemaining` never expires, and the specific error code on exhaustion. It also discloses that the allowance is PM-market scoped, which is non-obvious.

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?

The lead sentence front-loads the core answer, then cadence, then exhaustion behavior, then the related tool — a logical progression with no filler. It is dense and noun-heavy (wallet-sides, PM, FILL_ALLOWANCE_EXHAUSTED), which costs a little readability but every sentence carries distinct information.

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, the description supplies everything an agent needs: what is returned, reset cadence, success/failure semantics, and market scope. It does not waste space re-explaining return values that the output schema already documents.

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 the baseline is 4 and there is no input semantics to clarify. The description does add meaning to the returned fields (`freeRemaining`, `paidRemaining`, `period`, `resetsAt`), though an output schema exists, so that is a bonus rather than a requirement.

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?

The description opens with a specific verb+resource: reporting how many executed wallet-sides the calling agent has left, including `freeRemaining`, plus what buying PM adds. It explicitly scopes the tool ('Only PM markets read or debit this allowance') and points to `kellian_buy_play_money` for the related action, so an agent can distinguish it from balance or order tools without reading 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 Guidelines5/5

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

It states the condition that matters for tool selection: at zero, an ordinary NEW PM order is refused with FILL_ALLOWANCE_EXHAUSTED, while cancellations, resting-order execution and verified full-position closes remain available. It also names the remedy path via `kellian_buy_play_money`, so both when-to-use and what-to-do-next are explicit.

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?