Aman G.

Thanks for your response, Anthony P.. In my tool call definition, I referenced one parameter within the description of another, using it as a condition. According to several sources, OpenAI processes parameters from top to bottom. If a key is referenced before it's defined, it can lead to hallucinations and incorrect responses. I tested this by rearranging the parameter order, and when defined correctly, it worked as expected. In my case, the value of certain keys should depend on another key—either being null or an object—but it always returns null regardless.

Posted in Phoenix Support·

Aman G.

·

Preserving Order in Tool Definitions: JSON vs JSONB Solutions

Hi, I'm encountering an issue with tool definitions. In my tool, some parameter keys are dependent on others, as referenced in their descriptions—so the order of keys is important. However, Phoenix stores tool definitions in a JSONB column, which automatically reorders the keys (typically by key length), and this is causing the tool to malfunction. Is there a way to preserve the key order or work around this issue? Also, would it be possible to use a JSON column instead of JSONB to maintain the original key order?

19Comments

Posted in Discussions·

Aman G.

·

Preserving Order in Tool Definitions: JSON vs JSONB Solutions

Hi, I'm encountering an issue with tool definitions. In my tool, some parameter keys are dependent on others, as referenced in their descriptions—so the order of keys is important. However, Phoenix stores tool definitions in a JSONB column, which automatically reorders the keys (typically by key length), and this is causing the tool to malfunction. Is there a way to preserve the key order or work around this issue? Also, would it be possible to use a JSON column instead of JSONB to maintain the original key order?

1Comment