liveBook · Manning

Tool usage

As explained in Authorization in Action

A tool invocation is a request by an agent or software system to execute an operation provided by an external tool.

Tool usage is an agent’s request to perform an operation outside the model itself. Tools can retrieve documents, query databases, call internal APIs, or trigger automated workflows; the agent selects them while pursuing a goal. section 18.2

Structured interfaces describe each operation with a name, description, and input schema. The Model Context Protocol (MCP) lets an agent discover and invoke tools through a common interface while the MCP server translates requests into system-specific API calls. section 18.2

Document search

An agent invokes documents.search with a customerId and query. The MCP server maps that request to ACME’s document-search API and returns results in an agent-usable form. section 18.2

How Authorization in Action covers it

How deep it goes
Defines invocation and structured integration, but defers the authorization decision governing whether a call is allowed.
Examples
Uses document search, database queries, calendar access, internal APIs, and automated workflows as tool examples.
What you can do after
Operate structured tool integrations by discovering capabilities and invoking them with defined inputs.
How it connects
Connects agents with external systems, APIs, MCP, structured schemas, and authorization.

Also explained in

Compare how 13 books explain tool usage →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Authorization in Action. The section links point to the parts of the book it draws on.