Skip to main content
Glama

compare_prospects

Compare two NBA draft prospects skill by skill, showing each edge and modeled probability for reaching Top 25%; flag skills as not-comparable when either player lacks reliable data.

Instructions

Side-by-side comparison of two players, skill by skill, with the edge (which player, and by how much modeled probability of reaching Top 25%) for each skill. If either player abstains on a skill (out of distribution, or too little data), that skill is marked not-comparable instead of picking a winner. skills defaults to all four (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_a": "<player_a>",
      "player_b": "<player_b>"
    },
    "name": "compare_prospects"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillsNo
player_aYes
player_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 meaningful behavior: abstentions (out-of-distribution or thin data) are marked not-comparable rather than forcing a winner. It also explains how the edge is expressed. It does not cover error behavior for unknown player identifiers or what the comparison result structurally 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?

Front-loaded with the core purpose, then the definitional detail about edges and abstention, then the parameter default. Four tight sentences with no filler; slightly repetitive in restating 'for each skill' and 'that skill' twice.

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 no-annotation, no-output-schema tool, the description explains the comparison semantics and result meaning reasonably well. The main gap is the identifier ambiguity on the two required parameters, which an agent needs settled before calling; nothing covers invalid-player handling.

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%, and player_a/player_b are documented only by their titles, so the description does not clarify whether they accept names, IDs, or slugs. It does add real value for `skills` by naming the four valid values and stating the default (all four), which the schema does not do, but that compensates for only one of three parameters.

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?

States a concrete verb and resource: 'Side-by-side comparison of two players, skill by skill,' plus what the output conveys (edge as modeled probability of reaching Top 25%). That is specific enough to separate it from siblings like get_skill_profile or search_players, though no sibling is named explicitly.

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 tool is for comparing two specific players across skills. There is no explicit statement of when to prefer this over get_skill_profile, find_comps, or project_custom_prospect, and no prerequisites or exclusions are given.

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