-
-
Notifications
You must be signed in to change notification settings - Fork 7
MCP Dynamic Tools #49
Copy link
Copy link
Open
Labels
A-MCPModel Context Protocol toolingModel Context Protocol toolingC-FeatureA new feature, making something new possibleA new feature, making something new possibleM-Needs-Release-NoteWork that should be called out in the blog due to impactWork that should be called out in the blog due to impactS-Adopt-MeThe original author has no intent to complete this work. Pick me up!The original author has no intent to complete this work. Pick me up!
Description
Metadata
Metadata
Assignees
Labels
A-MCPModel Context Protocol toolingModel Context Protocol toolingC-FeatureA new feature, making something new possibleA new feature, making something new possibleM-Needs-Release-NoteWork that should be called out in the blog due to impactWork that should be called out in the blog due to impactS-Adopt-MeThe original author has no intent to complete this work. Pick me up!The original author has no intent to complete this work. Pick me up!
Currently types of content are hardcoded as ContentType and CrateMeta, being able to create tool descriptions based on a config file will allow us to move beyond the hardcoded types, and allow the user to define these in the
beet.toml.A good place to start might be checking out the MCP Rust SDK to see if dynamic tools are a thing.
Also I'm hoping to remove all
toolboxandschemarsmacros, preferingbevy_reflectwhen we need to do schema stuff but have no idea if/how that would work.