Skip to main content
Glama

search_players

Resolve misspelled or unverified NBA player names to canonical names before querying other scouting tools, and confirm whether each player is covered by the model.

Instructions

Resolve a (possibly misspelled) player name to one or more canonical names. Use this FIRST for any player you don't have an exact, verified name for. Every other tool here accepts a canonical name and will return candidates instead of guessing if the name is ambiguous or not found. The college pipeline runs 1985-2019 and NBA outcomes 1996-2025, so very recent or very old players may not be covered; this tool tells you whether a player is in the model's training set, in the 2018 draft holdout, or neither.

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": {
      "query": "<query>"
    },
    "name": "search_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the training data windows (1985-2019 college, 1996-2025 NBA), that coverage gaps exist for very recent or old players, and that the tool reports training-set vs 2018 draft holdout vs neither. It does not state whether the call is read-only or what the candidate list looks like on failure beyond 'return candidates', leaving a small gap.

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?

Five sentences, each carrying a distinct piece of information: purpose, priority, downstream behavior, data scope, and coverage interpretation. It is slightly dense and could front-load the coverage caveat better, but there is no padding.

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 lookup tool with no annotations and no output schema, the description covers purpose, sequencing, downstream contract, and data coverage limits. The main omission is any indication of return shape (list size, matching on failure) and the undocumented limit parameter.

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?

Schema coverage is 0%, so the description must compensate. It clarifies that 'query' is an approximate/misspelled name and that multiple results can come back, which is meaningful framing the schema lacks. The 'limit' parameter (default 5) is never mentioned, so the compensation is incomplete.

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: resolve a possibly misspelled player name to one or more canonical names. It also explains the output semantics (canonical names), which distinguishes it clearly from siblings like compare_prospects or find_comps that consume names rather than resolve them.

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 an explicit ordering instruction ('Use this FIRST for any player you don't have an exact, verified name'), explains what other tools do when given a bad name, and describes how to interpret coverage outcomes. That is when-to-use, what-happens-otherwise, and how-to-read-results in one place.

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