Tools missing on discovery of MCP?

[majerus1223]

When I add an MCP lets say like grafana, it should have 50 tools. However when I add it to contextforge is has 45. It seems to be missing the update tools.

I removed the MCP and scoped it to team as a test to see if that would change things which it did not.

Is there something that is guarding destructive tools from being displayed? Trying to work around this and a few other things wonder if I stumbled accross something that is part of the platform or bug. Thanks!

Direct connection to the MCP, 50 tools listed.

Tools available in context forge

[majerus1223]

I guess this is why?

{"asctime": "2026-03-30T13:37:49", "name": "mcpgateway.services.gateway_service", "levelname": "ERROR", "message": "Validation failed for tool 'update_dashboard': [{'type': 'value_error', 'loc': ('description',), 'msg': \"Value error, Description contains unsafe characters: ';'\", 'input': 'Create or update a dashboard. Two modes: (1) Full JSON \u2014 provide \\'dashboard\\' for new dashboards or complete replacements. (2) Patch \u2014 provide \\'uid\\' + \\'operations\\' to make targeted changes to an existing dashboard. One of these two modes is required; \\'folderUid\\'\\\\, \\'message\\'\\\\, and \\'overwrite\\' are supplementary and do nothing on their own. Patch operations support JSONPaths like \\'$.panels[0].targets[0].expr\\'\\\\, \\'$.panels[1].title\\'\\\\, \\'$.panels[2].targets[0].datasource\\'. Append to arrays with \\'/- \\' syntax: \\'$.panels/- \\'. Remove by index: {\"op\": \"remove\"\\\\, \"path\": \"$.panels[2]\"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues.', 'ctx': {'error': ValueError(\"Description contains unsafe characters: ';'\")}, 'url': 'https://errors.pydantic.dev/2.12/v/value_error'}]", "@timestamp": "2026-03-30T13:37:49.884286Z", "hostname": "mcp-stack-mcpgateway-695f8f79f9-858qz", "process_id": 1, "request_id": "2daa71464de5416ebd375b3e10bbcefa"}

[majerus1223]

Suppose related to #3770

[bogdanmariusc10]

Hello, @majerus1223 ! I created a PR for the aggressive tool description validation issue: #3916

[majerus1223]

Awesome, i added this to limit strict validation to the config, readded the MCP and it works as expected. Thank you for the PR