Skip to content

Add enums to Model Info tool#1

Closed
geoffharcourt wants to merge 8 commits into
mainfrom
gh-enums-in-model-info-tool
Closed

Add enums to Model Info tool#1
geoffharcourt wants to merge 8 commits into
mainfrom
gh-enums-in-model-info-tool

Conversation

@geoffharcourt

Copy link
Copy Markdown
Member

One of the most common reasons to need to use the Console Executor
rather than the Safe Query tool is to get the values of enums on models.
This change adds the enums to the Model Info tool's output so to
increase the chance that the LLM query can be accomplished wholly by the
combination of the Model Info tool and the Safe Query tool without
requiring Ruby eval/execution of user-supplied code.

@geoffharcourt geoffharcourt marked this pull request as ready for review March 31, 2026 16:51
@geoffharcourt

Copy link
Copy Markdown
Member Author

Note: failures will be resolved after the MCP upgrade change is merged.

One of the most common reasons to need to use the Console Executor
rather than the Safe Query tool is to get the values of enums on models.
This change adds the enums to the Model Info tool's output so to
increase the chance that the LLM query can be accomplished wholly by the
combination of the Model Info tool and the Safe Query tool without
requiring Ruby eval/execution of user-supplied code.
@geoffharcourt geoffharcourt force-pushed the gh-enums-in-model-info-tool branch from 1bb162c to c0b4417 Compare April 1, 2026 12:46
@geoffharcourt geoffharcourt force-pushed the gh-enums-in-model-info-tool branch from c0b4417 to f186c30 Compare April 1, 2026 12:49
@geoffharcourt geoffharcourt force-pushed the gh-enums-in-model-info-tool branch from deb8c63 to 34f07af Compare April 1, 2026 12:50
@geoffharcourt

Copy link
Copy Markdown
Member Author

Closed, merged upstream!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant