ci: real MCP tool-listing smoke test - #48
Merged
Merged
Conversation
Replace the shallow `import cubrid_mcp_server` smoke with a real-usage check that constructs the FastMCP server and enumerates its registered tools via `mcp.list_tools()`, asserting all 10 documented tools are present. Tool handlers connect to CUBRID lazily, so the tool surface is verifiable without a live database or CUBRID_* env vars. Closes #43 follow-up (real MCP usage smoke).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the shallow
import cubrid_mcp_serversmoke check insmoke-test.ymlwith a real-usage smoke test that constructs the FastMCP server object and enumerates its registered tools viamcp.list_tools(), asserting all 10 documented tools are present.Why
A bare
importonly proves the module loads — it silently passes even if the@mcp.toolregistration surface is broken (e.g. a tool fails to register, is renamed, or dropped upstream). Listing the tool surface exercises the actual server contract.How it stays DB-free
Tool handlers connect to CUBRID lazily (only on first call via
_db()), so enumerating the tool surface needs no live database and noCUBRID_*env vars. Verified locally against the pinned@v0.2.1install (fastmcp 3.4.6): prints 10 tools, exits 0.Tool contract asserted
all_table_names,filter_table_names,schema_definitions,describe_table,list_indexes,explain_query,table_row_counts,list_serials,list_class_hierarchy,execute_queryTest plan
yaml.safe_load)@v0.2.1git install — exits 0, lists 10 tools