Default input fragments applied before a handler runs.
Developer and model-facing explanation of the value.
JSON Schema text supplied by a peer or caller.
Port name used by handlers and on the wire.
Whether callers must provide the port.
MIME-facing type description.
Whether the port carries at most one value.
Validate the port contract and autofill fragments.
StaticcreateConstruct and validate a port schema.
Contract for one named action input or output node.
Port descriptions and types form the interface shown to application code and, commonly, to an LLM tool schema.
unaryguides consumers toward one whole value while streaming ports may yield many fragments. Input autofills can supply defaults before the handler runs, but the runtime rejects an autofilled input that already contains data.