Skip to main content
Gumloop uses your tool’s return type to generate an output schema. This schema tells Gumloop what data your tool produces, enabling it to connect your tool’s output to other nodes in workflows. Without proper type annotations, these connections break.

Schema Mapping

Here’s how different return types translate to schemas:

Examples

See how different return types generate schemas that Gumloop can use.
Generated schema:

Lists

Typed dicts

Primitives

Primitives are wrapped in a result key:
Output: {"result": 17}

What to Avoid

These patterns will cause problems in Gumloop because they don’t generate usable schemas:
These tools work for direct MCP calls but break Gumloop workflows because there’s no schema for node connections.

Field Descriptions

Make your output easier to understand by adding descriptions to fields. These show up in Gumloop’s UI and help users know what each field contains: