Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ai/gen-ai-agents/custom-rag-agent/start_ui_mcp.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
streamlit run ui_mcp_agent.py

2 changes: 2 additions & 0 deletions ai/gen-ai-agents/mcp-oci-integration/start_aggregator.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
python mcp_aggregator.py

2 changes: 2 additions & 0 deletions ai/gen-ai-agents/mcp-oci-integration/start_mcp_consumption.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
python mcp_consumption.py --port 9500

2 changes: 2 additions & 0 deletions ai/gen-ai-agents/mcp-oci-integration/start_mcp_explorer.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
streamlit run mcp_explorer.py
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be more broadly used?

For FastMCP servers, I just use fastmcp dev ... and list tools / test tool calls. Wondering what the difference / advantages hand-rolling this are.


Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
python mcp_internet_search.py --port 8500


21 changes: 21 additions & 0 deletions ai/gen-ai-agents/open-agent-spec/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2025 Luigi Saetta

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
141 changes: 141 additions & 0 deletions ai/gen-ai-agents/open-agent-spec/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,141 @@
# 🧩 Open Agent Specification — Overview

A **unified declarative standard for AI agents**, designed to bring interoperability across frameworks such as **LangGraph**, **AutoGen**, and **Oracle Agent Runtime**.

> From fragmented agent frameworks to interoperable agentic systems
> 📄 Source: [arXiv 2510.04173 (October 2025)](https://arxiv.org/abs/2510.04173)

---

## 🎯 Design Objectives

| Objective | Description |
|------------|--------------|
| **Portability & Interoperability** | Move agents seamlessly between frameworks (LangGraph, AutoGen, OCI Agent Runtime). |
| **Declarative Definition** | Define agents in YAML/JSON instead of hardcoded logic. |
| **Modularity & Composability** | Reuse flows, tools, and sub-agents. |
| **Explicit Control & Data Flow** | Clearly define how steps connect, branch, or loop. |
| **Validation & Conformance** | Built-in schema validation ensures compatibility. |
| **Multi-Agent Composition** | Enable collaboration and orchestration among agents. |

---

## 🧠 Core Concepts and Components

| Concept | Explanation |
|----------|--------------|
| **Agent** | The reasoning or conversational entity. |
| **Flow** | Structured workflow defining execution steps (nodes, branches, loops). |
| **Tool** | API, function, or service the agent can call. |
| **Memory / Prompt Templates** | Mechanisms for contextual state and conversation history. |
| **Edges** | Define relationships and data flow between nodes. |

These building blocks form the **agent graph**, which can be executed on compatible runtimes.

---

## ⚙️ Serialization, SDKs, and Runtime Adapters

### Serialization Layer
- Uses **YAML/JSON schemas** for transparent, portable definitions.
- Supports versioning, validation, and interchange.

### Python SDK — `PyAgentSpec`
- Reference SDK for building, validating, and exporting agents.
- Provides schema validation, object composition, and serialization.

### Runtime Adapters
Bridge the specification to concrete frameworks:
- **OCI Agent Runtime**
- **LangGraph**
- **AutoGen**

Adapters support **import/export** interoperability:

---

## 🔄 Control Flow & Data Flow Semantics

- **Directed edges** define execution order.
- **Branching and loops** for dynamic logic.
- **Inputs/outputs** explicitly mapped between steps.
- **Nested flows** and **sub-agents** enable modular reuse.

This model ensures predictability, traceability, and easy debugging across runtimes.

---

## 💡 Benefits & Value Proposition

| Stakeholder | Benefits |
|--------------|-----------|
| **Developers** | Portability, validation, and reuse of components. |
| **Framework Vendors** | A standardized interchange format. |
| **Researchers** | Reproducibility and comparability across experiments. |
| **Enterprises** | Governance, modularity, and reduced vendor lock-in. |

> **In essence:** “Write once, run anywhere” for AI agents.

---

## ⚠️ Limitations & Challenges

| Challenge | Description |
|------------|--------------|
| **Early-Stage Adoption** | Specification is still experimental. |
| **Runtime Mismatch** | Execution semantics differ between frameworks. |
| **Performance Overhead** | Translation layer introduces minimal latency. |
| **Safety & Observability** | Delegated to runtime implementations. |

---

## 🗺️ Roadmap & Future Directions

Planned enhancements include:
- **Memory, Planning, and Datastore** extensions.
- **Agent-to-Agent (A2A)** communication protocols.
- SDKs for more languages (Java, TypeScript, Go).
- **Conformance tests** and **visual editors**.
- Community-driven **registry of agents**.

---

## 🔍 Critique & Strategic Considerations

### Strengths
- Framework-agnostic and modular.
- Promotes ecosystem collaboration.
- Declarative, composable design.

### Risks
- Slow adoption curve.
- Runtime complexity.
- Divergent adapter implementations.

### Recommendations
- Start small and modular.
- Contribute runtime adapters early.
- Prioritize **observability** and **safety instrumentation**.

---

## 🧾 Summary & References

The **Open Agent Specification** defines a **declarative, interoperable schema** for building modular AI agents across multiple runtimes and ecosystems.

| Resource | Link |
|-----------|------|
| 📄 Paper | [arXiv 2510.04173](https://arxiv.org/abs/2510.04173) |
| 💻 GitHub | [https://github.com/oracle/agent-spec](https://github.com/oracle/agent-spec) |
| 📘 Docs | [https://oracle.github.io/agent-spec/index.html](https://oracle.github.io/agent-spec/index.html) |
| 📰 Blog | [Oracle AI & Data Science Blog](https://blogs.oracle.com/ai-and-datascience/post/introducing-open-agent-specification) |

---

### ✅ Summary Statement

> **Open Agent Specification** is a key step toward **standardizing AI agent design**, enabling transparent, portable, and interoperable agent systems across enterprise and open-source ecosystems.

---


Loading