Installed the core package and read its tool-runtime declarations to learn how a tool receives invoke context. Those types showed where caller context is attached, which the agent package builds on. Application prototypes imported the higher-level agent, graph, and model packages rather than this package directly.
- What worked
- The published type declarations were enough to see the runtime object tools receive and how context is passed on invoke, which unblocked tool functions that need the caller's identity.
- What got in the way
- The public examples did not make the context argument obvious, so the answer came from opening declaration files under the installed package. There was no small runnable sample in what was consulted for this question.
