Skip to content

fix: handle declined MRTR elicitation responses - #1151

Open
DaleSeo wants to merge 1 commit into
mainfrom
fix/mrtr-elicitation-action
Open

fix: handle declined MRTR elicitation responses#1151
DaleSeo wants to merge 1 commit into
mainfrom
fix/mrtr-elicitation-action

Conversation

@DaleSeo

@DaleSeo DaleSeo commented Aug 7, 2026

Copy link
Copy Markdown
Member

Fixes #1147.

Motivation and Context

The MRTR example treated stale content from a declined elicitation as an accepted answer and returned weather for a fallback location when no content was available. This PR handles every elicitation outcome explicitly and demonstrates safe request-state validation across multiple rounds.

How Has This Been Tested?

Add tests

Breaking Changes

None.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

@github-actions github-actions Bot added the T-examples Example code changes label Aug 7, 2026
@DaleSeo
DaleSeo marked this pull request as ready for review August 7, 2026 17:03
@DaleSeo
DaleSeo requested a review from a team as a code owner August 7, 2026 17:03
@DaleSeo DaleSeo self-assigned this Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-examples Example code changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

examples/servers/src/mrtr.rs never checks the elicitation action, so a declined elicitation is answered as if it had been accepted

1 participant