Skip to main content
Glama
Sign In

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

My Sleeper League — your starters beside their Kalshi markets

my_league
Read-only

Use for "show my fantasy team" and "what is Kalshi pricing my starters at". Give a Sleeper username (and a league name if you have several): your roster, each starter's opponent and kickoff, OUT and QB-gate flags, and every Kalshi prop strike on him this week with the best price per side. Market data; Pro adds our weekly projection.

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": "my_league"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague name (partial) or Sleeper league id, when the user is in several.
sleeper_usernameNoSleeper username (profile → username, not the display name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint already declared, the description still adds real context: this is live market data, best price per side is computed, and weekly projections are gated behind Pro. It does not say whether prices are delayed, whether a missing/unknown username errors out, or how much data a response can carry.

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?

Two sentences, both earning their place, with the usage triggers front-loaded. The second sentence is a fairly dense comma-list of return fields, but each item is informative rather than filler.

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?

There is no output schema, so the description must describe return values and it does so thoroughly, including the tier-gated projection. Missing only edge behavior: no-username defaults, empty leagues, and whether an unresolvable league name fails or falls back.

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 coverage is 100% and both parameters are already documented, so the schema does the heavy lifting. The description only restates the username/league relationship; notably all parameters are optional and it never says what happens when sleeper_username is omitted, which is the one ambiguity the schema does not resolve.

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 states a concrete verb+resource pair ("show my fantasy team", Kalshi pricing for starters) and enumerates exactly what comes back: roster, opponent, kickoff, OUT/QB-gate flags, and prop strikes with best price. It implicitly separates itself from advice tools like start_sit by labeling the output "market data" rather than recommendations, though no sibling is named outright.

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

Usage Guidelines4/5

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

It gives explicit trigger phrases ("show my fantasy team", "what is Kalshi pricing my starters at") plus the input condition for the optional league argument ("if you have several"). There are no explicit when-not conditions or named alternatives such as start_sit or player_outlook, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Prediction Markets Quant toolsInspect
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