Support mapped enums for tool property input

Open on Drupal.org →

Created on 1 May 2025, 3 months ago

Problem/Motivation

In some cases, you want to use an enum, but the values don't have any explicit description, e.g. if constants are backed by integers. For the LLM to chose, it needs a description.

Proposed resolution

Expand the enum to support oneOf/anyOf with const/title so values can be described.

API changes

ToolsPropertyInputInterface::setEnum becomes slightly more permissive in the data types it takes.

Data model changes

The tool output sent to LLM will swap out oneOf/anyOf for mapped types.

✨ Feature request

Status

Active

Version

1.1

Component

Code

Created by

🇬🇧United Kingdom andrewbelcher

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Merge Requests

!578Support mapped enums for tool property input
Merged
🇬🇧United Kingdom andrewbelcher
updated 3 months ago

Comments & Activities

Issue created by @andrewbelcher
Merge request !578Issue #3522221 by andrewbelcher: Support mapped enums for tool property input → (Merged) created by andrewbelcher
Comment 3 months ago →
🇬🇧United Kingdom andrewbelcher
Pipeline finished with Success
3 months ago
Total: 202s
#486668
Pipeline finished with Success
3 months ago
Total: 198s
#486726
First commit to issue fork.
Comment 3 months ago →
🇩🇪Germany marcus_johansson
Thank you, added a small "and" to the error message. This is getting merged.
Comment 3 months ago →
System Message

marcus_johansson → committed 4de367c3 on 1.1.x authored by andrewbelcher →
Issue #3522221 by andrewbelcher: Support mapped enums for tool property...
Comment 2 months ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.
Issue was unassigned.
Status changed to Fixed 27 days ago5:08am 1 July 2025
Comment 27 days ago →
🇺🇸United States Kristen Pol Santa Cruz, CA, USA
We are doing some issue management housekeeping and adding/removing components.

We are removing the "Code" component and want people to categorize issues with the best module/submodule component.

Moving this issue to "Miscellaneous" as I'm not sure where the best place is.

If we have a new project to move this to, we can optionally do that as a secondary step.

See 📌 Update AI module project components Active for more details.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024