You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
8
8
## Introduction
9
9
10
-
The Universal Tool Calling Protocol (UTCP) is a modern, flexible, and scalable standard for defining and interacting with tools across a wide variety of communication protocols. UTCP 1.0.0 introduces a modular core with a plugin-based architecture, making it more extensible, testable, and easier to package.
10
+
The Universal Tool Calling Protocol (UTCP) is a secure, scalable standard for defining and interacting with tools across a wide variety of communication protocols. UTCP 1.0.0 introduces a modular core with a plugin-based architecture, making it more extensible, testable, and easier to package.
11
11
12
12
In contrast to other protocols, UTCP places a strong emphasis on:
13
13
@@ -87,7 +87,7 @@ Version 1.0.0 introduces several breaking changes. Follow these steps to migrate
87
87
3.**Update Imports**: Change your imports to reflect the new modular structure. For example, `from utcp.client.transport_interfaces.http_transport import HttpProvider` becomes `from utcp_http.http_call_template import HttpCallTemplate`.
88
88
4.**Tool Search**: If you were using the default search, the new strategy is `TagAndDescriptionWordMatchStrategy`. This is the new default and requires no changes unless you were implementing a custom strategy.
89
89
5.**Tool Naming**: Tool names are now namespaced as `manual_name.tool_name`. The client handles this automatically.
90
-
6**Variable Substitution Namespacing**: Variables that are subsituted in different `call_templates`, are first namespaced with the name of the manual with the `_` duplicated. So a key in a tool call template called `API_KEY` from the manual `manual_1` would be converted to `manual__1_API_KEY`.
90
+
6.**Variable Substitution Namespacing**: Variables that are substituted in different `call_templates`, are first namespaced with the name of the manual with the `_` duplicated. So a key in a tool call template called `API_KEY` from the manual `manual_1` would be converted to `manual__1_API_KEY`.
91
91
92
92
## Usage Examples
93
93
@@ -226,7 +226,7 @@ if __name__ == "__main__":
226
226
227
227
### 2. Providing a UTCP Manual
228
228
229
-
A `UTCPManual` describes the tools you offer. The key change is replacing `tool_provider` with `call_template`.
229
+
A `UTCPManual` describes the tools you offer. The key change is replacing `tool_provider` with `tool_call_template`.
230
230
231
231
**`server.py`**
232
232
@@ -288,7 +288,7 @@ def utcp_discovery():
288
288
"conditions": {"type": "string"}
289
289
}
290
290
},
291
-
"call_template": {
291
+
"tool_call_template": {
292
292
"call_template_type": "http",
293
293
"url": "https://example.com/api/weather",
294
294
"http_method": "GET"
@@ -311,7 +311,7 @@ You can find full examples in the [examples repository](https://github.com/unive
311
311
312
312
### `UtcpManual` and `Tool` Models
313
313
314
-
The `tool_provider` object inside a `Tool` has been replaced by `call_template`.
314
+
The `tool_provider` object inside a `Tool` has been replaced by `tool_call_template`.
315
315
316
316
```json
317
317
{
@@ -324,7 +324,7 @@ The `tool_provider` object inside a `Tool` has been replaced by `call_template`.
0 commit comments