Tool descriptions are missing in versions after 0.1.3 using streamable-http

[pranav-td]

I notice that many tools are missing to show their descriptions in versions later than 0.1.3.
Below is the log from Github-Copilot in VS Code:

2025-09-12 22:16:14.095 [info] Starting server teradataHttp
2025-09-12 22:16:14.098 [info] Connection state: Starting
2025-09-12 22:16:14.123 [info] Starting server from LocalProcess extension host
2025-09-12 22:16:14.125 [info] Connection state: Running
2025-09-12 22:16:14.195 [info] Discovered 35 tools
2025-09-12 22:16:14.195 [warning] Tool sql_Analyze_Cluster_Stats does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.195 [warning] Tool sql_Execute_Full_Pipeline does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.196 [warning] Tool sql_Retrieve_Cluster_Queries does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.196 [warning] Tool dba_databaseSpace does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.196 [warning] Tool dba_resusageSummary does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.196 [warning] Tool dba_tableSpace does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.197 [warning] Tool dba_tableSqlList does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.197 [warning] Tool dba_tableUsageImpact does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.197 [warning] Tool dba_userSqlList does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.197 [warning] Tool qlty_columnSummary does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.198 [warning] Tool qlty_distinctCategories does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.199 [warning] Tool qlty_missingValues does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.199 [warning] Tool qlty_negativeValues does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.199 [warning] Tool qlty_rowsWithMissingValues does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.199 [warning] Tool qlty_standardDeviation does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.200 [warning] Tool qlty_univariateStatistics does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.200 [warning] Tool rag_Execute_Workflow does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.200 [warning] Tool base_columnDescription does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.200 [warning] Tool base_databaseList does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.200 [warning] Tool base_readQuery does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.200 [warning] Tool base_tableAffinity does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.200 [warning] Tool base_tableDDL does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.201 [warning] Tool base_tableList does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.201 [warning] Tool base_tablePreview does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.201 [warning] Tool base_tableUsage does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.201 [warning] Tool tmpl_nameOfTool does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.201 [warning] Tool sec_rolePermissions does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.201 [warning] Tool sec_userDbPermissions does not have a description. Tools must be accurately described to be called
2025-09-12 22:16:14.202 [warning] Tool sec_userRoles does not have a description. Tools must be accurately described to be called

Contents of my MCP config file in VS Code:

{
	"servers": {
		"teradataHttp": {
			"type": "http",
			"url": "http://127.0.0.1:8001/mcp"
		}
	}
}

[dtehan-td]

@remi-td, I checked and VS Code is missing the descriptions, it is hard to tell with Claude, so I was going to Inspector and ran into a problem when running: uv run mcp dev ./src/teradata_mcp_server/app.py

I got the following error:
No server object found in /Users/Daniel.Tehan/Code/MCP/teradata-mcp-server/src/teradata_mcp_server/app.py. Please either:

1. Use a standard variable name (mcp, server, or app)
2. Specify the object name with file:object syntax3. If the server creates the FastMCP object within main() or another function, refactor the FastMCP object to be a global variable named mcp, server, or app.

Checking into this:
What the error means
The runner (uv) imports your module and looks for a module-level server object named mcp, server, or app. Your server.py creates the FastMCP instance inside main() and only runs it when the module is executed as a script:
create_mcp_app(settings) is called inside async main()
at module import time there is no global variable mcp, server, or app
therefore the runner cannot find a server object and emits: "No server object found..."
In short: uv imports the file to inspect it, but the FastMCP instance is only created at runtime inside main(), so nothing is exposed at import time.
Why this matters
Runners that auto-discover apps expect an actual object to be present at import time. If the creation is buried inside a function guarded by if name == "main" (or only inside main()), import-time discovery will fail.
Fix options (brief, pick one)
Expose a module-level mcp instance
Create a top-level mcp variable (and optionally logger) by calling create_mcp_app(...) at import time (often using env-derived settings).
Pros: simplest for auto-discovery; uv will find mcp automatically.
Cons: import-time side effects (DB connections, optional heavy imports). Mitigate with try/except fallback to a lightweight FastMCP placeholder.

Not sure I want to make changes until we talk about the suggestions.