Skip to content

[BFCL] Ground truth rejects valid enum values in live_parallel and live_simple #1314

Description

@bhavishya-pohani

Summary

9 entries in the live categories have ground truth accepted values that reject outputs that are valid per the function specification. Two issues:

1. cmd_controller.execute — default not in enum (4 entries)

live_simple_141-94-0, live_simple_143-95-0, live_simple_156-95-13, live_simple_159-95-16

The unit parameter has enum: ["seconds", "milliseconds"] and default: "N/A". The default value "N/A" is not a member of the enum. The ground truth only accepts "" or "N/A", rejecting "seconds" which is a valid enum value.

2. get_current_weather / get_snow_report — celsius rejected (3 entries)

live_parallel_3-0-3, live_parallel_6-3-0, live_parallel_13-9-0

The unit parameter has enum: ["celsius", "fahrenheit"], default: "fahrenheit". The ground truth only accepts "" or "fahrenheit", rejecting "celsius". In 2 of 3 cases the queried locations are in Celsius countries (Mexico — prompt is in Spanish; France), making "celsius" a reasonable choice.

3. Two additional entries

  • live_simple_241-125-4: play_spotify_song function description says "It should be formatted as 'track:Song Name artist:Artist Name' for specific searches" but the ground truth only accepts the bare song name.
  • live_simple_59-28-0: get_movies(movie_date=) spec says "Default is the current date." User asks for movies "today." GT only accepts "" or null, rejecting a concrete date string.

I have a detailed markdown with the full function definitions, model outputs, and GT accepted values for all 9 entries — happy to attach if helpful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions