Skip to main content
Glama

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Explain a Player Ranking

explain_player
Read-only

Explain WHY the 2026 draft board ranks a player where it does, factor by factor: projection, floor/ceiling band, boom/bust week shape, and the three separate ranks a board row carries — our model's own positional rank, the market's ADP, and the published blend between them — plus the edge between model and market. Also states what the projection does NOT model (injuries, camp news, schedule). Free, no key. Use for "why do you have there", "explain ranking", "what's driving 's projection", "why is a sleeper/bust". For a plain outlook or a verdict rather than the reasoning, use player_outlook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / platform
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "enum": [
-        "yahoo",
-        "espn",
-        "sleeper",
-        "nfl",
-        "cbs",
-        "fantrax",
-        "draftkings",
-        "underdog"
-      ],
-      "type": "string"
-    }
-  ],
-  "description": "League platform — applies its default scoring, size, roster + best-ball settings (overridable by explicit scoring/teams). Underdog/DraftKings are best ball. One of: yahoo · espn · sleeper · nfl · cbs · fantrax · draftkings · underdog."
-}
    • removedInput schema / properties / player
      Removed value: -{
-  "description": "Player full name (e.g. \"Bijan Robinson\", \"Jaxon Smith-Njigba\").",
-  "type": "string"
-}
    • removedInput schema / properties / scoring
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "enum": [
-        "standard",
-        "half_ppr",
-        "ppr"
-      ],
-      "type": "string"
-    }
-  ],
-  "description": "Scoring format: standard, half_ppr (default), or ppr (full PPR). Overrides a platform preset. Works for Yahoo/ESPN/Sleeper defaults. One of: standard · half_ppr · ppr."
-}
    • removedInput schema / required
      Removed value: -[
-  "player"
-]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that the tool is 'Free, no key' and explicitly states what the projection does NOT model (injuries, camp news, schedule). These behavioral limitations add meaningful context an agent could not infer from the annotations or schema.

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 description is dense but each part earns its place: purpose, factors, limitations, key/access info, example phrases, and alternative tool. It is somewhat long, but front-loads the primary purpose and keeps the alternative guidance near the end, making it useful without excessive digression.

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?

For a zero-parameter, no-output-schema tool, the description covers its purpose, output contents, limitations, and alternative tools thoroughly. The only minor gap is that it doesn't explicitly state how the target player is identified when calling the tool, but the examples imply the player is present in the user query or conversation context.

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 has zero parameters and an empty schema, so the baseline for this dimension is 4. The description doesn't need to explain schema parameters and instead clarifies that the caller refers to a player in natural-language terms, which is sufficient for the no-parameter situation.

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 states a specific verb ('Explain WHY...') and a specific resource (the 2026 draft board ranking), enumerating the exact factors that are produced. It also differentiates from the sibling player_outlook by saying this is about reasoning, not a plain outlook or verdict.

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 gives explicit when-to-use patterns ('why do you have <player> there', 'explain <player> ranking', 'why is <player> a sleeper/bust') and an explicit when-not-to-use pointer ('For a plain outlook or a verdict rather than reasoning, use player_outlook'). This leaves no ambiguity about how the agent should route requests.

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