Skip to main content
Glama

explain_tier

Explains a player-skill tier prediction with top SHAP feature contributions, raw values and percentiles, archetype distance, and nearest comparable players so agents can justify scouting claims.

Instructions

Why the model predicts what it predicts: the top 5 feature contributions (SHAP) for this player and skill, each feature's raw value and training-set percentile, the player's archetype and distance to its centroid, and the 3 nearest comparable players in archetype space with their actual NBA tiers. This is the model's reasoning, not just its answer. Use it when an agent needs to justify a scouting claim. skill is one of Shooter, Rebounding, Playmaking, Defense.

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>",
      "skill": "<skill>"
    },
    "name": "explain_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYes
playerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the returned artifacts in detail, including the counterintuitive point that comparable players come with their actual NBA tiers. It does not cover failure modes such as an unknown player or a skill with insufficient data, nor does it indicate cost or latency for a SHAP computation.

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?

Every clause earns its place by naming a distinct returned element, and the purpose is front-loaded before the usage hint. The ordering is slightly awkward, since the `skill` enum constraint sits after the when-to-use sentence and reads as an afterthought rather than a parameter note.

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 two-parameter read tool with no annotations and no output schema, the description supplies the output shape in enough detail that an agent knows what it will get back and can quote it in a justification. The remaining gap is input-side: acceptable `player` formats and behavior on unknown players are unstated.

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 0% and the schema declares no enums, so the description's enumeration of `skill` as one of Shooter, Rebounding, Playmaking, Defense is a genuine addition that prevents an invalid call. However, `player` remains completely unspecified (name vs. ID, case sensitivity, ambiguity handling), so half the surface is still undocumented.

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 framing ('Why the model predicts what it predicts') and then enumerates exactly what is returned: SHAP top-5 contributions, raw value plus training-set percentile, archetype and centroid distance, and 3 nearest comparable players with their NBA tiers. This makes it clearly distinct from siblings like get_skill_profile (the answer) and find_comps (comps alone).

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?

'Use it when an agent needs to justify a scouting claim' gives a concrete triggering condition tied to a real workflow. It stops short of explicit exclusions or naming siblings (e.g., when to prefer get_model_card for global rather than per-player reasoning), so the agent must infer those boundaries.

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