From the tool schemas:
list_issues.includeArchived → "default": truelist_projects.includeArchived → "default": false
Other tools carrying the parameter follow list_projects.
The inconsistency is the problem rather than the value: an agent that learns the default from any other tool has it backwards for the tool it calls most, and archived issues silently enter result sets meant to be live-only. Because the parameter is optional, nothing at the call site reveals the difference.
Suggested fix
Default list_issues.includeArchived to false for consistency with its siblings. If the current default is deliberate for backwards compatibility, saying so in the parameter description would be enough to remove the trap — today the description is just "Include archived items" on both tools, which reads as though the behaviour matches.
From the tool schemas:
list_issues.includeArchived→"default": truelist_projects.includeArchived→"default": falseOther tools carrying the parameter follow
list_projects.The inconsistency is the problem rather than the value: an agent that learns the default from any other tool has it backwards for the tool it calls most, and archived issues silently enter result sets meant to be live-only. Because the parameter is optional, nothing at the call site reveals the difference.
Suggested fix
Default
list_issues.includeArchivedtofalsefor consistency with its siblings. If the current default is deliberate for backwards compatibility, saying so in the parameter description would be enough to remove the trap — today the description is just "Include archived items" on both tools, which reads as though the behaviour matches.