Hi@tommaso-moro, thank you so much for the detailed review and suggestions!

I've updated the PR following your recommendations:

• ✅State →Closed (Boolean)
• ✅AnsweredAt → Removed (usinganswerChosenAt instead)

RegardingisAnswered:

Following your suggestion to use the GraphQL API Explorer, I tested the available fields and found thatisAnswered is actually a valid field in the Discussion type.

Evidence:

1. Official Documentation: TheGitHub GraphQL Reference listsisAnswered (Boolean) as a field for Discussion objects.

2. GraphQL Query Test: I tested with both answered and unanswered discussions:

query {repository(owner:"github",name:"github-mcp-server") {discussion(number:1248) {isAnsweredanswerChosenAt       }     }   }

• Answered discussion (1248):{ "isAnswered": true, "answerChosenAt": "2025-10-20T09:57:37Z" }
• Unanswered discussion (1088):{ "isAnswered": false, "answerChosenAt": null }

Both queries executed successfully without errors, confirming thatisAnswered is valid.

Given this, I've keptisAnswered as a direct field query rather than deriving it. This approach uses the field that GitHub's API provides and is more efficient than client-side calculation.

Would you prefer I derive it fromanswerChosenAt != nil instead, or is this approach acceptable?

Thank you again for your help! 🙏