Skip to main content
Glama

get_skill_profile

Retrieve a player's skill-by-skill NBA draft scouting profile, including predicted tier, class probabilities, confidence, archetype, and known NBA outcome from college box-score stats.

Instructions

Full skill-by-skill scouting profile for one player: predicted tier (Bottom 25% / Middle 50% / Top 25% of all NBA players at that skill), class probabilities, confidence, the actual NBA outcome when known, and the player's archetype. Tiers are relative to the full 1996-2025 NBA population at that skill, not to the player's draft class. Defense is the model's weakest skill, so expect lower confidence there. Uses college box-score stats only.

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": {
      "player": "<player>"
    },
    "name": "get_skill_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: it defines the tier baselines ('relative to the full 1996-2025 NBA population at that skill, not to the player's draft class'), discloses a known model weakness ('Defense is the model's weakest skill, so expect lower confidence there'), and states data provenance ('Uses college box-score stats only'). It stops short of covering failure behavior for an unknown player name or any latency/compute expectations.

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 output contents are front-loaded in the first sentence and the caveats follow in descending order of importance. The long parenthetical defining the three tier buckets is justified because it prevents a misreading of 'tier,' though the description runs slightly long for a one-parameter tool.

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 and no annotations, so the description must explain returns itself, and it does so thoroughly, including confidence caveats and population baselines. The remaining gap is input-side: nothing describes valid player identifier formats or error behavior, which matters given the 0% schema coverage.

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 0% for the single 'player' parameter, so the description must compensate and it only partly does. 'For one player' confirms the parameter is a single-player identifier, but nothing states the expected format (full name vs. ID), matching behavior, or what happens if the name is ambiguous or not found.

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 ('Full skill-by-skill scouting profile for one player') and then enumerates exactly what the payload contains: predicted tier, class probabilities, confidence, actual NBA outcome, and archetype. The 'one player' scope and 'skill-by-skill' framing clearly separate it from sibling tools like compare_prospects and search_players without needing to name them.

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: the phrase 'for one player' signals this is a single-player lookup rather than a comparison or search. There is no explicit when-to-use/when-not guidance, no mention of alternatives such as explain_tier or find_comps, and no stated preconditions for the player lookup.

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