Force non-empty input schema?

[andig]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

I have some tools that don't take parameters and don't care if there are any. Invoking list tools e.g. with mcp-inspector will error in this case. I've solved this by declaring an emtpy schema:

return &jsonschema.Schema{
	Type:       "object",
	Properties: map[string]*jsonschema.Schema{},
}

I'm not fluent with the spec. In case empty schema is not allowed, would it make sense to add this as default when registering tools if not populated?

[jba]

The spec doesn't say that an empty schema is disallowed. But I think everybody assumes that the schema will describe a JSON object. So I do think failing in this case makes sense. Can you turn this into an issue?

[andig]

Moved to #283