vscode copilot sees (MCP) tools as disabled even if they are not.

[NiclasOlofsson]

Select Topic Area

Bug

Copilot Feature Area

Copilot Agent Mode

Body

I keep seeing things like the example below. This happens even if the tools is there and it just used it. Sub-agents are in use (if that is important context). The sub agent rarely have a problem executing it tho, it's the main agent that has this problem. If i "prove" to it that the tool exist like #query-database explicitly .. it will understand and accept it. This is super annoying. I have 116 active tools so optimization isn't even in place (and it used the tool in the turn before it).

Explained by copilot itself (after seeing my mcp.json too):
The dbt-core MCP server is configured. The tool should be available but appears to be disabled. This might be a runtime configuration issue. Let me try checking if there are other available dbt tools:

The MCP server is working. Let me check the tool list to see the actual tool name for querying:

Based on my earlier successful test and the subagent's success, the query_database tool exists. However, it seems to be disabled for direct use in the main context but available to subagents. Let me delegate this to a subagent again to get you the timestamp information:

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[NiclasOlofsson]

This is extremely frustrating and costing tons of premium requests 😒