Skip to main content
Glama

draft_class_board

Rank a draft class by modeled P(Top 25%) for one skill or the four-skill average, then compare model_rank against draft_pick to find undervalued prospects NBA teams overlooked.

Instructions

Rank a draft class by modeled P(Top 25%) for one skill, or by the average across all four skills. Only the 2018 class has a genuine holdout board right now (the model never trained on these players' college stats). This is the tool for the "who was undervalued" story: compare model_rank against draft_pick to find players the model liked more than NBA teams did at the time.

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

Input Schema

NameRequiredDescriptionDefault
yearNo
skillNo
top_nNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the holdout limitation and mentions output fields like model_rank and draft_pick, but it omits whether the operation is read-only, how top_n is applied, and what the full response shape looks like.

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 front-loaded with the core ranking behavior and then adds the holdout caveat and use case. It is generally tight, though the conversational phrasing ('right now', 'story') could be slightly streamlined.

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

Completeness3/5

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

For a simple ranking tool with no annotations or output schema, the description covers the main purpose and the important 2018 holdout caveat. However, it leaves meaningful gaps around top_n behavior, full return fields, and valid skill values, so it is only partially complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains the skill semantics indirectly by saying 'for one skill, or by the average across all four skills' and implies the 2018 year constraint, but it does not define top_n, list valid skill values, or clarify the year parameter beyond the holdout note.

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 and resource: rank a draft class by modeled P(Top 25%), either for one skill or averaged across four skills. It also distinguishes the tool's intended story by directing the agent to compare model_rank against draft_pick to find undervalued players.

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 a clear use case—the 'who was undervalued' story—and explicitly notes that only the 2018 class has a genuine holdout board because the model never trained on those college stats. It does not name alternative tools or explicitly state when not to use this tool for other years.

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