Actions

Actions are callable operations exposed by your manifests. They wrap provider APIs or internal logic with a typed interface that LLMs and tools can use reliably.

Core ideas

• Schema-first: Each action defines name, description, input schema, and output schema.
• Auth integration: Actions can declare an auth provider (OAuth/device) and required scopes; tokens are injected at runtime.
• Manifest membership: Actions are included/excluded per manifest version to control exposure.

Where to manage

• Dashboard → Actions: Create/edit actions, set schemas, and test.
• Dashboard → Manifests → [manifest] → Actions: Include/exclude actions and publish versions.
• Dashboard → Action Library / Action Packs: Import prebuilt actions and curated packs.

Tips

• Keep input schemas minimal and validate at the edge; use enums for common choices.
• Use provider templates to prefill auth and base URLs.
• Test with the Developers page (MCP/A2A) or the Test MCP chat.