Skip to main content
Glama

Search Players & Teams

search
Read-onlyIdempotent

Use this when you need a player_id or team_id, or the user names a player or team you have not resolved yet ('Jokic', 'Lamar Jackson', 'BOS'); it is accent- and typo-tolerant. Returns up to six matching players and four teams per league with their numeric ids (players_more and the like say there are more: narrow the query); each list's page is a template such as player_url with the id in place of {id}. Not for stats: call player_profile or team_profile with the id.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPlayer or team name or abbreviation (e.g. "Jokic", "Lamar Jackson", "BOS").
leagueNoOptional league filter ("nba" or "nfl"). Omit to search both leagues.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description is free to add genuinely new behavior: accent- and typo-tolerant matching, a hard result cap of six players and four teams per league, the `players_more`-style truncation flags, and the `{id}` URL template in results. These are the details an agent needs to interpret and act on the response, none of which the annotations supply.

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?

Three sentences, front-loaded with the trigger condition before the return-shape detail and the exclusion. It is dense but nearly every clause carries information; the parenthetical example list of names overlaps with the schema examples and is the only mild redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of explaining return values, and it does: result counts, truncation flags, and the URL template. For a two-parameter lookup tool, nothing an agent needs in order to call it or read its output is missing.

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 100%, so the baseline would be 3; the description goes beyond it by characterizing matching behavior (typo/accent tolerance) and by explaining that results are capped per league, which motivates the optional league filter. It does not add format rules or edge cases for `query` beyond the schema's own examples.

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?

States a specific verb and resource (resolve a player or team name to a numeric id) and names the sibling tools it is not (player_profile, team_profile). An agent can distinguish this from every listed sibling without opening a schema.

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?

Gives an explicit trigger condition ("you need a player_id or team_id, or the user names a player or team you have not resolved yet") and an explicit exclusion with the correct alternative ("Not for stats: call player_profile or team_profile with the id"). Nothing is left to inference.

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