is_tools_api 0.2.1
is_tools_api: ^0.2.1 copied to clipboard
An intersyntactic tool's definition, as a host offers it to a model: its name, description, input and output, and the types of what a call takes and returns.
Changelog #
0.2.1 #
- Exports checked_json's
JsonObjectandJsonFieldException, and nothing else of it:Input.readtakes the one and throws the other, andToolSpec.toJsonreturns aJsonObject, so a package that depends on this one alone can name them. - The package description says what 0.2.0 holds: a tool's input and output, and the types of what a call takes and returns.
0.2.0 #
ToolSpec<I, O>is a tool's definition only: its name, description,inputandconcurrent, and the types of what a call takes,I, and returns,O.ToolSpec.run,ToolContext,ToolImageandToolProcessTapare removed: the code that answers a call, and what a call reports while it runs, belong to the airlock, which attaches it through the definition so that it must take anIand return anO.Input<I>,Field<T>andSchema<T>replace the hand-writteninputSchemamap: one description gives both the JSON Schema the model is shown and the reader that turns what it sent into anI, with every constraint the schema shows checked by the reader.inputSchemais nowinput.schema.Output<O>turns theOa call returns into the text of its tool result, once per tool;Output.textis for an answer that is already text. A failed call has noO: whoever runs the call reports it.- The library comment says kit for a host's set of tools.
0.1.0 #
- First release:
ToolSpec,ToolContext,ToolImageandToolProcessTap, the contract intersyntactic's tools are written against.