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
List all dynamically registered tools from the Swagger specification.
95
+
NOTE:
96
+
# LLM Context Note:
97
+
# When a user requests to "list all finetuning jobs", you (the LLM) must:
98
+
# 1. Call `list_dynamic_swagger_tools(ctx)` to get all available Swagger-based tools.
99
+
# 2. Parse the returned list and automatically select the tool whose name, path, or description matches the intent (such as "list finetuning jobs").
100
+
# 3. Call `execute_dynamic_swagger_action(ctx, tool_name=...)` with the selected tool's operation ID.
101
+
# This process is fully automated and does not require user or developer intervention.
102
+
# If no matching Swagger tool is found, return an error message.
103
+
104
+
# When a user requests to "get finetuning job events", you (the LLM) must:
105
+
# 1. Call `list_dynamic_swagger_tools(ctx)` to get all available Swagger-based tools.
106
+
# 2. Parse the returned list and automatically select the tool whose name, path, or description matches the intent (such as "get finetuning job events").
107
+
# 3. Call `execute_dynamic_swagger_action(ctx, tool_name=..., job_id=...)` with the selected tool's operation ID and required parameters.
108
+
# This process is fully automated and does not require user or developer intervention.
109
+
# If no matching Swagger tool is found, return an error message.
110
+
111
+
# When a user requests to "fetch finetuning job status", you (the LLM) must:
112
+
# 1. Call `list_dynamic_swagger_tools(ctx)` to get all available Swagger-based tools.
113
+
# 2. Parse the returned list and automatically select the tool whose name, path, or description matches the intent (such as "fetch finetuning job status").
114
+
# 3. Call `execute_dynamic_swagger_action(ctx, tool_name=..., job_id=...)` with the selected tool's operation ID and required parameters.
115
+
# This process is fully automated and does not require user or developer intervention.
116
+
# If no matching Swagger tool is found, return an error message.
117
+
Returns:
118
+
JSON string with list of available tools
119
+
"""
120
+
swagger_generator=get_swagger_generator()
121
+
122
+
ifswagger_generatorisNone:
123
+
returnjson.dumps({
124
+
"error": "No Swagger tools have been registered",
125
+
"hint": "Ensure SWAGGER_PATH is set in your .env file"
List all dynamically registered tools from the Swagger specification.
320
-
NOTE:
321
-
# LLM Context Note:
322
-
# When a user requests to "list all finetuning jobs", you (the LLM) must:
323
-
# 1. Call `list_dynamic_swagger_tools(ctx)` to get all available Swagger-based tools.
324
-
# 2. Parse the returned list and automatically select the tool whose name, path, or description matches the intent (such as "list finetuning jobs").
325
-
# 3. Call `execute_dynamic_swagger_action(ctx, tool_name=...)` with the selected tool's operation ID.
326
-
# This process is fully automated and does not require user or developer intervention.
327
-
# If no matching Swagger tool is found, return an error message.
328
-
329
-
# When a user requests to "get finetuning job events", you (the LLM) must:
330
-
# 1. Call `list_dynamic_swagger_tools(ctx)` to get all available Swagger-based tools.
331
-
# 2. Parse the returned list and automatically select the tool whose name, path, or description matches the intent (such as "get finetuning job events").
332
-
# 3. Call `execute_dynamic_swagger_action(ctx, tool_name=..., job_id=...)` with the selected tool's operation ID and required parameters.
333
-
# This process is fully automated and does not require user or developer intervention.
334
-
# If no matching Swagger tool is found, return an error message.
335
-
336
-
# When a user requests to "fetch finetuning job status", you (the LLM) must:
337
-
# 1. Call `list_dynamic_swagger_tools(ctx)` to get all available Swagger-based tools.
338
-
# 2. Parse the returned list and automatically select the tool whose name, path, or description matches the intent (such as "fetch finetuning job status").
339
-
# 3. Call `execute_dynamic_swagger_action(ctx, tool_name=..., job_id=...)` with the selected tool's operation ID and required parameters.
340
-
# This process is fully automated and does not require user or developer intervention.
341
-
# If no matching Swagger tool is found, return an error message.
342
-
Returns:
343
-
JSON string with list of available tools
344
-
"""
345
-
swagger_generator=get_swagger_generator()
346
-
347
-
ifswagger_generatorisNone:
348
-
returnjson.dumps({
349
-
"error": "No Swagger tools have been registered",
350
-
"hint": "Ensure SWAGGER_PATH is set in your .env file"
0 commit comments