AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

microsoft-foundry

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent, managed harness agent, Copilot harness, voice agent, create/update/invoke/evaluate agent, add tool to agent, agent insights, batch/continuous eval, continuous monitoring, agent CI/CD, optimize/improve prompt, optimize agent instructions, Agent Optimizer, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare).

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--microsoft-foundry at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 151

foundry-agent/create/references/tools/prompt-agent/agent-tools.md

Agent Tools

This file is the index for every tool an agent can use. For each tool, it points to a dedicated reference file, and — where the tool is also available through a toolbox — lists the toolbox type value.

Two delivery paths exist:

  • Prompt agent — the agent definition declares tool classes directly (CodeInterpreterTool, MCPTool, …). Use the SDK class column and the per-tool reference.
  • Hosted agent via toolbox — the agent connects to a single MCP endpoint that exposes all tools declared in a toolbox version. Use the type column and see use-toolbox-in-hosted-agent.md. For wiring the underlying project connection (catalog tile or generic remote MCP), see foundry-tool-catalog.md.

💡 Authoritative tool shapes: the source-of-truth for every tool's wire shape is the Foundry Agents typespec on the main branch of Azure/azure-rest-api-specs. When in doubt about a field name, default, or new tool type that isn't yet documented here, load the typespec directly — it's updated as tools are added/changed.

Tool Summary

| Tool | Prompt-agent SDK class | Connection? | Reference | |------|------------------------|-------------|-----------| | Code Interpreter | CodeInterpreterTool | No | tool-code-interpreter.md | | Function calling (client-side) | FunctionTool | No | tool-function-calling.md | | File Search | FileSearchTool | No (vector store required) | tool-file-search.md | | Web Search (preview) | WebSearchPreviewTool | No (basic Bing); Yes for Grounding with Bing Custom Search — the connection scopes grounding to specific domains | tool-web-search.md | | Bing Grounding | BingGroundingTool | Yes (Bing) | tool-bing-grounding.md | | Azure AI Search | AzureAISearchTool | Yes (Search) | tool-azure-ai-search.md | | MCP server (remote) | MCPTool | Optional (none / static key / project MI / OAuth) | tool-mcp.md; toolbox attach via foundry-tool-catalog.md | | OpenAPI tool | (n/a as a single class) | Conditional — connection auth requires project_connection_id; managed_identity auth does NOT (the project MI is used directly with an audience) | tool-openapi.md | | Agent-to-Agent (A2A) | (n/a as a single class) | Optional | tool-a2a.md | | Agent Memory | MemorySearchPreviewTool | Yes (project MI + embedding model) | tool-memory.md | | Work IQ (preview) | WorkIQPreviewTool | Yes (Work IQ BYO-Entra-app OAuth connection) | tool-work-iq.md | | Fabric IQ (preview) | FabricIQPreviewTool | Yes (Fabric IQ Entra-app OAuth or managed-OAuth connection) | tool-fabric-iq.md |

⚠️ Default for web search: Use WebSearchPreviewTool (type: web_search) unless the user explicitly requests Bing Grounding or Bing Custom Search.

How to use this index

When you need details for a specific tool, load that tool's reference file directly — each one is self-contained (shape, requirements, references). Don't try to keep all tools in context at once.

Adjacent (not a type in a toolbox version)

  • Agent Memory — use the MemorySearchPreviewTool SDK class on prompt agents; for hosted agents, configure the memory store via the project (separate from the toolbox). See tool-memory.md.
  • Routines (preview) — not a tool; an agent trigger (schedule / timer / github_issue / custom) that invokes an existing agent. Event-based routines are powered by the same Connector Namespace that backs catalog-MCP / managed-MCP connectors. See the public Routines docs.

References