Variable TOOL_INPUT_SHAPEConst
TOOL_INPUT_SHAPE: {
scenario: ZodString;
params: ZodOptional<ZodRecord<ZodString, ZodUnknown>>;
context: ZodOptional<ZodRecord<ZodString, ZodUnknown>>;
ext: ZodOptional<ZodRecord<ZodString, ZodUnknown>>;
} = ...
Type Declaration
scenario: ZodString
params: ZodOptional<ZodRecord<ZodString, ZodUnknown>>
context: ZodOptional<ZodRecord<ZodString, ZodUnknown>>
ext: ZodOptional<ZodRecord<ZodString, ZodUnknown>>
Canonical Zod input schema for the
comply_test_controllertool. Pass as theinputSchemaargument toserver.registerTool(...)in custom wrappers so the request shape stays in sync with registerTestController.Matches
ComplyTestControllerRequestfrom the generated schema:scenario(required),params(scenario-specific), and the universalcontext/extenvelope fields. No top-levelaccountorbrand— AdCP routes account and brand context throughcontexton this tool.Extending for vendor fields. Custom wrappers that route sandbox gating or tenant scoping on top-level fields can extend the shape locally. Both
accountandbrandare commonly added — storyboard fixtures and v5-shaped wrappers often send them alongsideparams:Adopters routing through
createAdcpServerFromPlatform({ complyTest })pass the same fields viacomplyTest.inputSchema(seeComplyControllerConfig.inputSchemain@adcp/sdk/testing).This keeps the default registration protocol-compliant while giving wrapper authors a documented extension point.