loopengine 0.1.43 → 0.1.44
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,25 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: composio-large-outputs
|
|
3
|
-
description: How to retrieve a gateway tool's real output when its result says storedInFile is true instead of returning the data inline.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Gateway tools with a large result
|
|
7
|
-
|
|
8
|
-
Some gateway tools (Composio-sourced ones in particular) return a small
|
|
9
|
-
pointer object instead of their real output when the actual result is
|
|
10
|
-
too large to return inline:
|
|
11
|
-
|
|
12
|
-
```
|
|
13
|
-
{
|
|
14
|
-
"successful": true,
|
|
15
|
-
"storedInFile": true,
|
|
16
|
-
"tokenCount": 10234,
|
|
17
|
-
"outputFilePath": "/tmp/.../SOME_TOOL_OUTPUT_xxxxx.json"
|
|
18
|
-
}
|
|
19
|
-
```
|
|
20
|
-
|
|
21
|
-
When you see `storedInFile: true` in a tool result, the real data is
|
|
22
|
-
**not** in that object — it's in the file at `outputFilePath`. Call
|
|
23
|
-
`system_read_file` with that exact path to retrieve the actual content
|
|
24
|
-
before answering. Don't guess at an answer, summarize from the pointer
|
|
25
|
-
alone, or claim you don't have the data — read the file first.
|