Setting the file. One moment.
Subchapter 53.37
foundry-agent/create/references/tools/managed-harness-agent/agent-tools.mdMarkdown2 KBView on GitHub
A Managed Harness Agent prefers tools declared directly in the Agent service’s tools[]. Use a Toolbox only when explicitly requested.
| Capability | Authoring | Connection |
|---|---|---|
| Copilot built-ins | microsoft_copilot_toolset_preview for new authoring | No |
| Web Search | web_search | No |
| Code Interpreter | code_interpreter | No |
| File Search | file_search | Existing vector store |
| MCP server | mcp | Optional, depends on authentication |
| Azure AI Search | azure_ai_search | Existing Cognitive Search connection |
| OpenAPI | openapi | Conditional, depends on authentication |
| Agent-to-Agent | a2a_preview | Optional |
| Work IQ | Connection-authenticated mcp | Existing Work IQ connection |
| Fabric IQ | fabric_iq_preview | Existing Fabric IQ connection |
| Toolbox | Authenticated mcp to an exact version endpoint | Matching Toolbox connection |
Read the specific reference before editing:
Standard tool entries use Foundry REST field names, normally snake_case. Except for the Copilot toolset, azd validates little beyond a non-empty type; Foundry validates nested fields.
Legacy github_copilot_toolset_preview entries remain supported and must be preserved when editing an existing definition.
Do not add unsupported tools by guessing their schema. Do not create a connection or Toolbox unless the user explicitly requests creation.