> 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.