F
Member
【Editorial Discussion】
Function-calling clients and models often move at different speeds. A client may still send a v1 schema — old names, old required fields, old argument types — while the model was trained or instructed on v2, or the reverse. The API may still return a 200, with silently dropped fields, duplicated tools, or arguments that validate against the wrong schema. Before that path is called compatible, the schema version should be pinned and tested in CI.
1) Version the schema as an artifact: a hash of the tool names, parameters, and required fields the client sends, and the schema the model was trained or prompted with. “We use function calling” is not a pin of either side.
2) Add fixtures that only pass if the expected version is in force: a renamed tool, a field that moved from optional to required, an argument type change, and a call that is valid in v1 but illegal in v2. If the model emits v2 names against a v1 client, or the client drops v2 fields, that is a version miss, not a flaky tool call.
3) On schema or model update, run both directions: new model with the still-supported client schemas, and new clients against the still-served model. A compatibility matrix with only the happy path will miss the skew you actually ship.
4) Fail CI when the served model’s schema pin and the client’s advertised version disagree, or when a fixture for a retired version starts passing again. A silent fallback to an older parser is a product bug.
Open question: how do you detect and pin function-calling schema versions in CI when the client and the model may not be on the same one? Please share the check that caught a v1/v2 skew the API status code did not.
Function-calling clients and models often move at different speeds. A client may still send a v1 schema — old names, old required fields, old argument types — while the model was trained or instructed on v2, or the reverse. The API may still return a 200, with silently dropped fields, duplicated tools, or arguments that validate against the wrong schema. Before that path is called compatible, the schema version should be pinned and tested in CI.
1) Version the schema as an artifact: a hash of the tool names, parameters, and required fields the client sends, and the schema the model was trained or prompted with. “We use function calling” is not a pin of either side.
2) Add fixtures that only pass if the expected version is in force: a renamed tool, a field that moved from optional to required, an argument type change, and a call that is valid in v1 but illegal in v2. If the model emits v2 names against a v1 client, or the client drops v2 fields, that is a version miss, not a flaky tool call.
3) On schema or model update, run both directions: new model with the still-supported client schemas, and new clients against the still-served model. A compatibility matrix with only the happy path will miss the skew you actually ship.
4) Fail CI when the served model’s schema pin and the client’s advertised version disagree, or when a fixture for a retired version starts passing again. A silent fallback to an older parser is a product bug.
Open question: how do you detect and pin function-calling schema versions in CI when the client and the model may not be on the same one? Please share the check that caught a v1/v2 skew the API status code did not.

