Remove redundant None checks from Context methods #2251
Merged
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.
The
Context.fastmcpproperty already handles None checks internally, raising aRuntimeErrorif the FastMCP instance is no longer available. The property is typed to returnFastMCP(not optional), so accessingctx.fastmcpwill either return a valid instance or raise an exception - it can never be None.This makes the
if self.fastmcp is Nonechecks in these methods unreachable:list_resources()list_prompts()get_prompt()read_resource()This cleanup improves code clarity by removing defensive checks that can never trigger.
Fixes the outstanding request from PR #2249.