ParallelCS Start here

HomeTracksAgentic Systems EngineeringTool Use & Function Calling

Week 2 concept

Tool Use & Function Calling

Give a model hands: structured tool schemas, argument validation, error feedback loops, and parallel tool calls. The contract between a model and the outside world is an API design problem.

Bridges to Software Engineering — interface design and API contracts

Builds on: The Augmented LLM as a Building Block

Study notes

Master this concept.

Tool Use & Function Calling

What it is

Tool use is the mechanism that allows a Large Language Model (LLM) to interact with external systems. While an LLM can predict text, it cannot natively browse a live database, send an email, or perform complex math. Function calling is the structured process where the model identifies which external tool to use and outputs the necessary arguments in a machine-readable format (typically JSON) to execute that action.

Why it matters

Without tools, an AI is a closed system limited to its training data. Tool use transforms a chatbot into an agent capable of taking action in the real world. It moves the system from "simulating" an answer to "retrieving" or "executing" a factual result, which drastically reduces hallucinations and allows the AI to integrate with existing enterprise software and APIs.

Core concepts to master

  • Tool Schemas: The precise definition of a tool's purpose and its required parameters. The model relies on these descriptions to decide which tool fits the user's intent.
  • Argument Validation: The process of verifying that the model's output matches the required data types and constraints before the tool is actually executed.
  • Error Feedback Loops: The ability to pass execution errors (e.g., "API Timeout" or "Invalid ID") back to the model so it can correct its arguments and try again.
  • Parallel Tool Calling: The capability of a model to trigger multiple independent tools in a single turn to satisfy a complex request.

Common mistakes

  • Vague Descriptions: Writing tool descriptions that are too brief or ambiguous, leading the model to call the wrong function.
  • Over-reliance on the Model: Assuming the model will always produce perfect JSON. Robust systems must include a validation layer between the model and the API.
  • Ignoring State: Failing to feed the tool's output back into the conversation history, leaving the model unaware of the result of its own action.

Track connection

Tool use is the foundational "action layer" of Agentic Systems Engineering. It bridges the gap between the reasoning engine (the LLM) and the execution environment. Once mastered, it enables more advanced patterns like autonomous planning, multi-step reasoning chains, and self-correcting agent loops.

Notes written for this concept by the ParallelCS in-house model. Always cross-check against the linked sources below.

Go to the source

Read, watch, and practice.

Free, world-class material chosen for this concept.

Back to the Agentic Systems Engineering plan