StrikerAPI

Squad

get_squad

Read-onlyIdempotent

Use for a club's current squad, or every club's in the league when team is left out: every registered player with position, shirt number, date of birth, age, citizenship, height and weight, including players not yet named in a matchday squad (new signings, youth players), and how many of the club's matches each has played this season. Refreshed weekly. For the players in one match use get_lineups. Costs 2 credits for a club, 10 for the whole league.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_squad"
  }
}

Input Schema

Name	Required	Description
`team`	No	Club id, abbreviation or name (list_teams). Leave out for every club in the league, with each player's team.
`league`	No	League. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
`position`	No	One position.

Output Schema

Name	Required	Description	Default
`note`	No
`team`	Yes
`count`	Yes
`season`	Yes
`players`	Yes
`team_id`	Yes
`team_name`	Yes
`updated_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 2, 2026

changedInput schema / properties / team / description

Previous value: -"Club id, abbreviation or name (list_teams)."New value: +"Club id, abbreviation or name (list_teams). Leave out for every club in the league, with each player's team."

removedInput schema / required
```
Removed value: -[
-  "team"
-]
```

changedOutput schema / properties / team / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / team_id / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / team_name / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds traits the annotations cannot: data freshness ('Refreshed weekly'), credit pricing per call shape, and the non-obvious inclusion rule that players not yet in a matchday squad (new signings, youth players) are still returned. That last point materially changes how an agent interprets a sparse result.

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 primary use case and the exclusion/alternative before the field inventory; the trailing cost and refresh sentences are short and decision-relevant. The long enumeration of returned fields is somewhat redundant given an output schema exists, which keeps it from a 5.

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?

Given three optional params, an output schema, and full annotation coverage, the description supplies everything left over: scope semantics, freshness, cost, and the inclusion rule for unregistered matchday players. No behavioral or selection-relevant detail is missing.

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 coverage is 100% and both enum parameters are fully documented in-schema, so the description only needs to compensate for gaps. It clarifies the semantic consequence of omitting team (league-wide sweep with each player's team), which matches the schema wording, but says nothing about the position filter or league defaulting, so it adds little beyond the structured fields.

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+resource ('club's current squad') plus the exact scope expansion when team is omitted (every club in the league), and explicitly names the sibling get_lineups as the match-level alternative. An agent can distinguish this from get_lineups, get_player, and get_team_stats without opening any 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 explicit when-to-use (club squad, or league-wide if team is left out), a named alternative with the condition that selects it ('For the players in one match use get_lineups'), and a cost trade-off (2 credits per club vs 10 for the whole league) that informs whether to scope by team.

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

All StrikerAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.