[Docs]: Unclear instructions to test a2a agent as mcp tool

[bayer-veera]

📚 Documentation Issue Summary

Document is not clear on how to test a2a agent as a mcp tool. When tested the virtual server doesn't return the a2a agent which is associated in the tool/list

📍 Location of the Problem

https://github.com/IBM/mcp-context-forge?tab=readme-ov-file#a2a-agent-to-agent-features

---

✏️ Type of Issue

• [ ] Typo or formatting issue
• [ ] Outdated or incorrect information
• [ ] Missing explanation or example
• [x ] Unclear instructions
• [ ] Other (explain below)

---

💡 Suggested Fix or Clarification (optional)

The documentation mentions this, but the examples invoke the agent directly through the admin API and not through the virtual server

https://github.com/IBM/mcp-context-forge?tab=readme-ov-file#a2a-agent-to-agent-features

🤖 A2A Integration: A2A agents are external AI agents that can be registered and exposed as MCP tools 🔄 Protocol Detection: Gateway automatically detects JSONRPC vs custom A2A protocols 📊 Testing: Built-in test functionality via Admin UI or /a2a/{agent_id}/test endpoint 🎛️ Virtual Servers: Associate agents with servers to expose them as standard MCP tools

---

🧠 Environment (optional)

0.8.0 Helm Deployment

Key	Value
Docs version	latest
Platform	Linux

---

🧩 Additional Notes (optional)