Skip to content

chore: cleanup of native support #597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rapid-killer-9 wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −23
Open

chore: cleanup of native support #597

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 2 additions & 6 deletions packages/toolbox-adk/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,11 +56,10 @@ agent = Agent(tools=[toolset])

The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.

You can explicitly select a protocol using the `protocol` option during toolset initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
You can explicitly select a protocol using the `protocol` option during toolset initialization. This is useful if you need to pin the client to a specific legacy version of MCP.

> [!NOTE]
> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
> * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.
> * **MCP Transports**: These options use **Model Context Protocol over HTTP**.
### Supported Protocols

Expand All @@ -72,11 +71,8 @@ You can explicitly select a protocol using the `protocol` option during toolset
| `Protocol.MCP_v20250326` | MCP Protocol version 2025-03-26. |
| `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |

> [!WARNING]
### Example


```python
from toolbox_adk import ToolboxToolset
from toolbox_core.protocol import Protocol
Expand Down
8 changes: 2 additions & 6 deletions packages/toolbox-core/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,11 +149,10 @@ All interactions for loading and invoking tools happen through this client.

The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.

You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to pin the client to a specific legacy version of MCP.

> [!NOTE]
> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
> * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.
> * **MCP Transports**: These options use **Model Context Protocol over HTTP**.

### Supported Protocols

Expand All @@ -164,11 +163,8 @@ You can explicitly select a protocol using the `protocol` option during client i
| `Protocol.MCP_v20250618` | MCP Protocol version 2025-06-18. |
| `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |

> [!WARNING]

### Example


```py
from toolbox_core import ToolboxClient
from toolbox_core.protocol import Protocol
Expand Down
8 changes: 2 additions & 6 deletions packages/toolbox-langchain/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,11 +96,10 @@ async with ToolboxClient("http://127.0.0.1:5000") as toolbox:

The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.

You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to pin the client to a specific legacy version of MCP.

> [!NOTE]
> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
> * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.
> * **MCP Transports**: These options use **Model Context Protocol over HTTP**.

### Supported Protocols

Expand All @@ -112,11 +111,8 @@ You can explicitly select a protocol using the `protocol` option during client i
| `Protocol.MCP_v20250326` | MCP Protocol version 2025-03-26. |
| `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |

> [!WARNING]

### Example


```py
from toolbox_langchain import ToolboxClient
from toolbox_core.protocol import Protocol
Expand Down
6 changes: 1 addition & 5 deletions packages/toolbox-llamaindex/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,10 +100,9 @@ async with ToolboxClient("http://127.0.0.1:5000") as toolbox:

The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.

You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to pin the client to a specific legacy version of MCP.

> [!NOTE]
> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
> * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.

### Supported Protocols
Expand All @@ -116,11 +115,8 @@ You can explicitly select a protocol using the `protocol` option during client i
| `Protocol.MCP_v20250326` | MCP Protocol version 2025-03-26. |
| `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |

> [!WARNING]

### Example


```py
from toolbox_llamaindex import ToolboxClient
from toolbox_core.protocol import Protocol
Expand Down
Loading