Expand description
Tools, tool sets, registry, and the tool-call parser.
Structs§
- Evidence
Trace - The evidence + rationale behind a tool’s decision.
- Explained
Tool - Middleware enforcing an
ExplainabilityPolicyon anyRichTool. Wraps without touching the inner tool’s constructor (cf.WalledTool). - Handoff
Tool - Keyword
Tool Strategy - v1: lexical filter. Returns tools whose name or description contains any of the keywords found in the user’s turn input. (Substring match in v0; promote to TF-IDF later.)
- Missing
Evidence - Raised when
ExplainabilityPolicy::Requireis violated. - Parsed
Tool Call - Permission
Spec - Static
Tool Strategy - v0: hand-picked fixed list of tools.
- Tool
Call Parser - Stateful streaming parser. Feed each
tool_call_deltavalue as it arrives; callfinishto drain the accumulated calls. - Tool
Descriptor - Descriptor advertised to the model. The schema is JSON-Schema shaped; per-provider renderers in this crate adapt it to OpenAI / Anthropic / Gemini call formats.
- Tool
Schema - JSON-Schema fragment for the tool’s arguments.
- ToolSet
- Versioned bundle. Lives behind an
Arcin the registry. - Tool
SetMeta - Free-form metadata attached to a tool set.
- Tool
SetRegistry - Thread-safe registry of versioned tool sets. Multiple versions of the same id can coexist; consumers pin the version they want.
Enums§
- Evidence
Ref - A reference to a piece of evidence behind a decision.
- Explainability
Policy - Per-tool/desk explainability requirement.
- Provider
- Tool
Control - Tool
Return - What a richer tool returns. Agents map this back into the message sequence and (optionally) the workflow state.
Constants§
- EVIDENCE_
KEY - Reserved artifact key under which the evidence trace is stored.
Traits§
- Rich
Tool - Tool
- A tool the agent may call. Tools are also
Callable, so they can stand in as workflow steps.
Type Aliases§
- DynTool
Arc<dyn Tool>— what the registry stores.