> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/sportmonks-ai-docs/mcp-server-beta/tools.md).

# Tools

The Sportmonks MCP server exposes 11 tools covering the most common football data needs. Every tool is available in Claude, Cursor, and Windsurf once the server is installed.

### Tool reference

| Page                            | Tools covered                                             |
| ------------------------------- | --------------------------------------------------------- |
| Search                          | `search`                                                  |
| Players, Teams & Leagues        | `get_player`, `get_team`, `get_league`                    |
| Squads                          | `get_squad`                                               |
| Fixtures                        | `get_matches`, `get_match_preview`, `get_fixture_details` |
| Standings, Seasons & Topscorers | `get_standings`, `get_historic_seasons`, `get_topscorers` |

### How to use tools

Tools are called automatically by the AI during a conversation. You don't invoke them directly - just ask a question in natural language and the AI picks the right tool.

```
Show me the current Premier League standings
```

The AI calls `get_standings` internally and returns the formatted table.

### Typical workflow

Most tasks follow this pattern:

1. **Search** - use `search` to find the ID of a team, player, or league by name
2. **Fetch** - use the relevant tool with that ID to get the data you need
3. **Combine** - chain tools together for richer results (e.g. get a league ID, then fetch its standings and topscorers)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sportmonks.com/v3/sportmonks-ai-docs/mcp-server-beta/tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.