Skip to main content
Glama

Search players

search_players
Read-onlyIdempotent

Use to find a player's id by name (accents optional), optionally within a club. Returns position, current club, last season and appearances. Costs 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
nameYesFull or partial name, e.g. Saka.
teamNoClub id, abbreviation or name.
limitNo
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
playersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the bar is low. The description contributes the cost model ('Costs 1 credit') and the shape of the result (position, club, last season, appearances), which an agent needs for planning; it does not mention match ambiguity or default result counts.

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 clipped sentences, purpose front-loaded, no filler. The return-field list slightly duplicates the output schema but doubles as a selection aid, so it broadly earns its place.

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 lookup with annotations, an output schema, and 75% param coverage, most of what an agent needs is present. The remaining gap is behavioral: what happens on partial/ambiguous name matches and how many results come back by default.

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 75% and the description adds genuinely new semantics: name matching tolerates missing accents, and the club filter is optional rather than required. The limit and league params are only covered by the schema itself, so nothing is added there.

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 specific verb and resource ('find a player's id by name'), plus scope details (accents optional, optionally within a club). The id-lookup-by-name framing implicitly separates it from get_player (by id) and get_squad, but 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?

Implies the use case (you have a name and need an id) but gives no explicit exclusions or pointer to get_player once an id is known, and says nothing about when to narrow with league or limit.

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.