ToolEntry data type definition #666

Closed
opened 2026-10-27 13:37:15 +00:00 by sam · 0 comments
Owner

Design and implement the ToolEntry data type carrying: name, toolset (which tool group this belongs to), schema (JSON Schema for invocation), handler (function ref), check_fn (availability predicate), requires_env (env vars needed), is_async (async/sync distinction), description, emoji, max_result_size_chars (per-tool result cap), and dynamic_schema_overrides (runtime schema mutations). This is the foundational type that everything in the tools subsystem builds upon.


Imported from beads archie-core-1786637493467-141-ffb91b17 · GitHub #162 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08

Design and implement the ToolEntry data type carrying: name, toolset (which tool group this belongs to), schema (JSON Schema for invocation), handler (function ref), check_fn (availability predicate), requires_env (env vars needed), is_async (async/sync distinction), description, emoji, max_result_size_chars (per-tool result cap), and dynamic_schema_overrides (runtime schema mutations). This is the foundational type that everything in the tools subsystem builds upon. --- _Imported from beads `archie-core-1786637493467-141-ffb91b17` · GitHub #162 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumtask labels 2026-10-27 13:37:15 +00:00
sam self-assigned this 2026-10-27 13:37:15 +00:00
sam closed this issue 2026-10-27 13:37:15 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#666