Agents as MCP Clients

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I see a lot of confusion about agents, skills, sub-agents and other related concepts as they are implemented in various frameworks, such as LangGraph or Strands. The confusing terms are leading to complex implementation and hard migration between frameworks.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Agents can be described as a combination of LLM, instructions, and tools, working in ReAct or other simple loop definitions. Tools are best defined as MCP tools, and therefore, agents should be defined as MCP clients, with additional definition of LLM and instructions.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Another level of abstraction is the ability to create a team of agents, by creating an MCP server, where each agent is a tool. Since we defined an agent as LLM, instructions, and a set of MCP servers, we can build specialized agents that each uses a different LLM, work under different instructions, and utilize different MCP servers. Using the MCP protocol, the agents can discover which other agents are available in their team, by reading the description of the tools, and call them in the same way they call other MCP tools. Each agent can forward any part of the original task to any of the other agents through this bridge. With the support of MCP tasks, such calls are easy to monitor, pool, and get the results, making the otherwise complex team orchestration, a standard MCP based workflow.

In interactive MCP clients such as Claude Desktop, the users can choose to read resources and trigger prompts to enrich the conversation context with additional relevant information. Once we define agents as MCP clients, we can instruct them to also read resources from each or any MCP server (for example, default agent:instructions, or agent:skill:code-review), and trigger prompts.

Additional context
Add any other context or screenshots about the feature request here.

The MCP perspective is not only semantic of shifting from agents with tools, to tools with instructions and LLM. It allows to describe the agentic framework with the minimal set of concepts (Occam's razor), and the development of the MCP spec toward this goal.

No files, tests, or entry points are named. Start by reviewing the proposed MCP-client model and its references to MCP servers, tools, resources, prompts, and tasks; the issue is not complete until the working group defines an agreed implementation scope and acceptance criteria.