Skip to main content
Glama

LUMA NBA Impact Metrics

search_players

Read-onlyIdempotent

Find players by (part of) name, accent-insensitive. Returns pid, name, first/last season, position group (G/W/B).

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 observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: accent-insensitive matching and the exact shape of the result set (pid, name, first/last season, position group), which matters because no output schema exists. It does not explain limit/pagination or ordering of matches, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight sentence pair with no filler; the core capability and matching rule are front-loaded, and the return fields are appended as a compact clause. Nothing is redundant.

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 simple two-parameter search with full annotation coverage, the definition covers purpose, matching semantics, and return fields. Gaps remain around how many results come back by default, what 'limit' does, and how ambiguous matches are ordered.

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%, so the description must carry parameter meaning. It does add real semantics for 'query' (partial name match, accent-insensitive), but the 'limit' parameter is never mentioned, leaving half the parameters undocumented anywhere.

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?

The description names a specific verb and resource ('Find players') plus the matching mode ('by (part of) name, accent-insensitive') and lists the returned fields. It is clear what the tool does, but it does not explicitly distinguish itself from siblings like 'player' or 'compare' that also deal with players.

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 'Find players by (part of) name' suggests the lookup scenario, but there is no explicit when-to-use statement, no exclusion, and no pointer to an alternative tool for exact-ID retrieval or comparison. The agent must infer the retrieval-by-name use case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources