-
Notifications
You must be signed in to change notification settings - Fork 52
feat: generate specific tools for operations #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This is the wrong way to tackle this as it just performs worse than the simpler implementation currently in use. It adds way too many tools and also creates complex input schema's which just lead to models having a hard time to work with this. Nice eye opener that I shouldn't overengineer this |
Reopening as I want to offer this as an alternative to just querying the complete schema |
See issue #4, should've allowed this from the start
cffcc73
to
3391568
Compare
While the shorthand McpServer is nice, it's not as nice to use for dynamic tool generation
Hi @blurrah! Do you have any plans to make this feature available? |
Yes I will but in a different form most likely by allowing .graphql files to be used as tool calls. Needs some more work sorry for the delay @itestyoy |
This change allows for specific tools based on operations in the schema. This is an alternative to just querying the schema completely, especially if your schema exceeds context windows.
Need to think on how to craft this API a bit more, possibly re-add arguments as you can just stack in operations