feature: add automatic operation ID shortening for LLM compatibility #167
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.
Describe your changes
Add max_operation_id_length parameter to FastApiMCP that automatically shortens long operation IDs to fit within LLM character limits. The implementation preserves semantic meaning by prioritizing the most specific path segments and using MD5 hashing for uniqueness.
This ensures compatibility with LLMs that have strict limits on function/tool names (e.g., 60-64 characters) while maintaining readability and preventing collisions.
Issue ticket number and link (if applicable)
#161 (replicate of ->) #64 #69
Before/After Example
Before
❌ LLM Error: Function name exceeds 64 character limit
After
✅ LLM Compatible: Function name fits within limits while preserving semantic meaning
Checklist before requesting a review