Bring back tools list_tables and describe_table for better Microsoft Copilot Studio support?

[derFunk]

Hi all,

list_tables and describe_table have been removed in 90d998e.

Actually these both tools are very helpful, especially dealing with systems that call MCP but don't support resources yet (fully), like Microsoft Copilot (Studio). It still might take a while until MS rolls out all MCP features in Copilot Studio.

Besides that, being kind of on par with the features of mcp-clickhouse is a plus when integrating more complex systems, because it reduces the need for describing Clickhouse DB in prompts.

Is there any bigger reason for not including these tools anymore? What would be the expected "workaround"?

[BorisTyshkevich]

Could you provide an example of why list/describe tool is important for Microsoft Copilot ? In my experience, all models can run show create table or show tables over the execute tool to discover the schema. What model are you using?

Having too many tools overloads the context window. Better have an absolute minimum, especially if you have many mcp servers connected in a chat. We definitely should create two tools (#35), and a growing list of tool descriptions sitting in the context window is a big problem.

The approach used in mcp-clickhouse with list/describe as tools is completely outdated by the situation of the MCP protocol specs and industry recognition at the end of 2025. Such a queries as show databases/tables should be translated to resources, not tools. You have to support resources fully if you want to be in line with MCP development.

[Slach]

@derFunk any news about your use cases?