feat: Add enum constraint to agent_name for transfer_to_agent
#2437
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current implementation of
transfer_to_agentdoesn't enforce strict constraints on agent names,We could use JSON Schema's enum definition to implement stricter constraints:
Before
[{ "type": "function", "function": { "name": "transfer_to_agent", "description": "Transfer the question to another agent.\n\nThis tool hands off control to another agent when it's more suitable to answer the user's question according to the agent's description.\n\nArgs:\n agent_name: the agent name to transfer to.\n", "parameters": { "type": "object", "properties": { "agent_name": { "type": "string" } } } } }]After
[{ "type": "function", "function": { "name": "transfer_to_agent", "description": "Transfer the question to another agent.\n\nThis tool hands off control to another agent when it's more suitable to answer the user's question according to the agent's description.\n\nArgs:\n agent_name: the agent name to transfer to.\n", "parameters": { "type": "object", "properties": { "agent_name": { "type": "string", "enum": ["agent_a", "agent_b", "agent_c"] } } } } }]