Refactor Resource/ResourceTemplate to subclass Annotated

[Redth]

The Resource and ResourceTemplate types should derive from a base Annotated type having the Annotations property as per the spec

This small change makes the C# types match the schema more closely.

Also renamed Resources.cs to Resource.cs to reflect the type name.

Motivation and Context

As per #20 refactoring these two types

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

[PederHP]

Looks correct to me. Also checked the Annotations type, just in case there was a discrepancy on that one too. It matches the spec, although the Min and Mix properties don't really have a equivalent in .NET, unless I there's a facility I don't know about. But it's documented in the comment. And it's tangential to this.

[stephentoub]

the Min and Mix properties don't really have a equivalent in .NET, unless I there's a facility I don't know about

Can you tell me more? What are these such that they don't have an equivalent?

[PederHP]

the Min and Mix properties don't really have a equivalent in .NET, unless I there's a facility I don't know about

Can you tell me more? What are these such that they don't have an equivalent?

"annotations": {
                    "properties": {
                        "audience": {
                            "description": "Describes who the intended customer of this object or data is.\n\nIt can include multiple entries to indicate content useful for multiple audiences (e.g., `[\"user\", \"assistant\"]`).",
                            "items": {
                                "$ref": "#/definitions/Role"
                            },
                            "type": "array"
                        },
                        "priority": {
                            "description": "Describes how important this data is for operating the server.\n\nA value of 1 means \"most important,\" and indicates that the data is\neffectively required, while 0 means \"least important,\" and indicates that\nthe data is entirely optional.",
                            "maximum": 1,
                            "minimum": 0,
                            "type": "number"
                        }
                    },
                    "type": "object"
                }

I don't know of an attribute (Range perhaps but it's not really used with JSON serialization afaik) that matches this pattern.

(I also think it's an oddly narrow property, as a Client author (as a service/app developer) I wouldn't know how to interpret this on a Resource from an arbitrary server).

[stephentoub]

I don't know of an attribute (Range perhaps but it's not really used with JSON serialization afaik) that matches this pattern.

Ah, I see. @eiriktsarpalis, is there something built-in you'd expect to be used here?