Skip to main content

Rust SDK Tools and Agents

Rust is a strong fit for Worka packs because it lets you expose typed tools cleanly and run them inside the platform’s container model without carrying unnecessary runtime overhead.

What the Rust SDK gives you​

In the current model, the Rust SDK helps you:

  • define tool inputs and outputs as real types
  • expose tools through an MCP server
  • return structured results
  • use the broker client for approved outbound or host-mediated operations

That gives you a cleaner contract than ad hoc JSON manipulation spread through your tool handlers.

Tool design guidance​

When building a Rust tool for Worka:

  • keep inputs narrow and explicit
  • return structured content that the rest of the platform can reuse
  • separate external API normalization from business decisions
  • avoid hiding side effects behind vague tool names

For example, list_issues or get_work are easier to understand than overly general tools like execute or handle_request.

Agents in pack code​

Some packs also define agent-facing behavior or helpers for AI team members. Keep the distinction clear:

  • the pack provides capability
  • the workspace and workflow decide which AI team member uses that capability and when

That separation makes the resulting workspace easier to govern.