nit: Add ListResourceTemplates to ClientRequest / ServerResult in schema.ts

[gsabran]

Based on my understanding of the specs, it seems that those values were forgotten in the ClientRequest / ServerResult type.

Motivation and Context

This change aligns schema.ts with the description of the specs found in https://spec.modelcontextprotocol.io/specification/server/resources/

How Has This Been Tested?

NA

Breaking Changes

Possibly breaking Typescript compilation for developers referencing ClientRequest / ServerResult. Still mostly a bug fix.

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

[jspahrsummers]

Absolutely, great catch. Thanks!

[jspahrsummers]

@gsabran Can you please just run npm run generate:json to update the JSON Schema? Then we can get this in. 🙏

[gsabran]

Ah yes I'll do

[gsabran]

Side question: do you think there's a need to clarify the results for SubscribeRequest and UnsubscribeRequest ? Maybe just as a comment that they map to EmptyResult (my understanding) ?

There is no SubscribeResult / UnsubscribeResult and I didn't the the response described in https://spec.modelcontextprotocol.io/specification/server/resources/#subscriptions either

[dsp-ant]

Side question: do you think there's a need to clarify the results for SubscribeRequest and UnsubscribeRequest ? Maybe just as a comment that they map to EmptyResult (my understanding) ?

There is no SubscribeResult / UnsubscribeResult and I didn't the the response described in https://spec.modelcontextprotocol.io/specification/server/resources/#subscriptions either

This might also be an oversight on our end.

addressed