Expose all tools at a single endpoint

[jirispilka]

It’s difficult to understand how the server works if you don’t know which tools are available, what their input parameters are, or what each tool does.

See Keboola’s list of tools for reference: https://github.com/keboola/mcp-server?tab=readme-ov-file#supported-tools

[] - Update the README to include a list of available tools
[] - Expose all tools at an endpoint, e.g., GET /tools

[MQ37]

Expose all tools at an endpoint, e.g., GET /tools

We could return a simple HTML page where we would render all the tools in a nice table on mcp.apify.com/tools and link that in the README. What do you think @jirispilka? Since lisitng tools in README.md is error-prone, you can easily forget to update the entries.

[jirispilka]

Sounds good, but from a user perspective, it adds extra effort.

So in the README, we should provide a generic description and, for details, link to a simple HTML page listing all the tools.

[MQ37]

we decided to rework this feature we will use ?dumpJson=1 query param and it will dump all the tools available for the current MCP url.