Skip to content

Conversation

h3xxit
Copy link
Member

@h3xxit h3xxit commented Sep 8, 2025

Summary by cubic

Adds a comprehensive OpenAPI ingestion guide and expands the README to show zero‑infrastructure conversion of OpenAPI 2.0/3.0 specs into UTCP tools using the utcp-http plugin and client config examples. Also clarifies CLI protocol docs (no implicit JSON parsing), marks CommandStep as REQUIRED in the CLI template, and tidies a test.

h3xxit and others added 3 commits September 7, 2025 17:26
* Add comprehensive OpenAPI ingestion documentation

- Add detailed OpenAPI ingestion guide with 5 different methods
- Include working code examples for all ingestion approaches
- Add prominent OpenAPI section to main README
- All code snippets tested and validated
- Zero infrastructure approach highlighted

* Simplify OpenAPI ingestion documentation

- Remove unnecessary duplication and complexity
- Focus on core functionality with minimal examples
- Reduce from verbose guide to concise reference
- All code snippets tested and working

* Clarify plugin dependencies in OpenAPI documentation

- Add plugin comments to all UTCP imports
- Show which imports come from core vs utcp-http plugin
- Clarify YAML loader also handles JSON files

---------

Co-authored-by: Razvan Radulescu <[email protected]>
@h3xxit h3xxit merged commit 908cd40 into main Sep 8, 2025
19 checks passed
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

1 issue found across 5 files

React with 👍 or 👎 to teach cubic. You can also tag @cubic-dev-ai to give feedback, ask questions, or re-run the review.

@@ -588,8 +587,7 @@ async def call_tool(self, caller, tool_name: str, tool_args: Dict[str, Any], too
Returns:
The result of the command execution. If the command exits with a code
of 0, it returns the content of stdout. If the exit code is non-zero,
it returns the content of stderr. The output is parsed as JSON if
possible; otherwise, it is returned as a raw string.
it returns the content of stderr.
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Sep 8, 2025

Choose a reason for hiding this comment

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

Docstring omits that successful stdout is parsed as JSON when possible; this line now misstates the function’s behavior, which returns parsed JSON via _parse_combined_output when the output looks like JSON.

Prompt for AI agents
Address the following comment on plugins/communication_protocols/cli/src/utcp_cli/cli_communication_protocol.py at line 590:

<comment>Docstring omits that successful stdout is parsed as JSON when possible; this line now misstates the function’s behavior, which returns parsed JSON via _parse_combined_output when the output looks like JSON.</comment>

<file context>
@@ -588,8 +587,7 @@ async def call_tool(self, caller, tool_name: str, tool_args: Dict[str, Any], too
             of 0, it returns the content of stdout. If the exit code is non-zero,
-            it returns the content of stderr. The output is parsed as JSON if
-            possible; otherwise, it is returned as a raw string.
+            it returns the content of stderr.
 
         Raises:
</file context>
Suggested change
it returns the content of stderr.
it returns the content of stderr. The output is parsed as JSON if possible; otherwise, it is returned as a raw string.
Fix with Cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants