Skip to content

Conversation

@LucaButBoring
Copy link
Contributor

The 11/25 spec release added the Tool.execution field, but neglected to mention it anywhere in the actual tools spec. This adds that to both the 11/25 and draft spec pages, as it does not imply any behavioral changes.

Motivation and Context

Communicates that Tool.execution is a field that exists.

How Has This Been Tested?

N/A

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

Additional context

@LucaButBoring LucaButBoring requested a review from a team as a code owner December 4, 2025 22:40
Copy link
Contributor

@He-Pin He-Pin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

]
],
"execution": {
"taskSupport": "optional"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be forbidden for it's the default behavior

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had considered that, but there wouldn't be much value there over not including it at all, so I figured I'd make it optional to show a deviation from the default here.

]
],
"execution": {
"taskSupport": "optional"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be forbidden for it's the default behavior

@localden
Copy link
Contributor

localden commented Dec 5, 2025

My only concern here is that this modifies the existing stable spec beyond the draft, but given thtat this is a documentation gap, it's less of an issue.

@dsp-ant - thoughts?

@localden localden added documentation Improvements or additions to documentation enhancement New feature or request labels Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants