fix: forward full JSON schema for function tool params to RubyLLM (2.0.5)

[obie]

What

Raix::FunctionToolAdapter rebuilt each function parameter field-by-field via RubyLLM's param(...), which only carried type and description. Rich JSON-Schema fields — additionalProperties, items, enum, and nested properties — were silently dropped.

The visible symptom: providers (notably Gemini structured output via OpenRouter) had no real schema for type: object arguments, so they invented degenerate shapes — e.g. emitting {"prefix" => false} instead of {"prefix:title" => "..."}.

Fix

Forward the full schema dict via RubyLLM's params(schema) path instead of rebuilding it.

That path forwards the schema verbatim and, unlike param(...), does not inject the OpenAI strict-mode guards. So the adapter now defaults additionalProperties: false and strict: true at the outer schema (preserving prior behavior), while letting a function declaration override either by setting it explicitly.

params({ additionalProperties: false, strict: true }.merge(function_def[:parameters]))

Tests

New spec/raix/function_tool_adapter_spec.rb covers:

• Rich JSON-Schema fields (additionalProperties on nested object params) survive to params_schema
• Outer strict-mode guards (additionalProperties: false, strict: true) preserved by default
• No-parameter functions still produce no schema

Full suite: 107 examples, 0 failures, 1 pending. RuboCop clean.

Versioning

2.0.4 was already released upstream for an unrelated change, so this cuts 2.0.5 and rolls the pending temperature-default fix out of [Unreleased] into [2.0.5] alongside this fix.

🤖 Generated with Claude Code