We don't publish
your competitive advantage.

IFTool output contains special character \x85 (NEXT LINE) causing httpx decoder to truncate SSE payload

THENReplace \x85 and similar Unicode line break characters (e.g., \u0085) in tool responses before serialization, or ensure JSON encoding escapes these characters properly.

IFStorageContext.persist fails with TypeError: Object of type float32 is not JSON serializable when a Document has an embedding that is a numpy float32 array.

THENConvert the embedding to a Python list of floats before passing it to the Document constructor. In custom embedding models, ensure the return value is a list rather than a numpy array. For example, replace the direct output with [float(x) for x in embedding] or set return_type='list' if available.

IFEvery MCP response from a Python SDK-based server causes a JSON parse error: 'Expected ',' or ']' after array element in JSON' on the client side.

THENEnsure that the MCP server output is a pure, well-formed JSON object with no leading whitespace, newlines, or BOM characters before the JSON. In the Python SDK, verify that the serialization function (e.g., json.dumps) is called directly without additional print statements or buffering that could insert extraneous characters.