androidengineers.Book a session

Tool schemas and execution loops

Lab: implement a guarded tool registry

exerciseSelf-paced

Assignment

Create read_ticket and propose_update tools over an in-memory sandbox, with a durable operation store simulated by SQLite.

Build sequence

  1. Validate names and arguments before execution.
  2. Represent error categories explicitly and limit retries for transient failures.
  3. Simulate a timeout after a mutation commits.
  4. Replay the same operation ID and verify its result is reused.

Acceptance checks

  • Unknown tools and unauthorized actors never reach business logic.
  • A post-commit timeout does not create duplicate mutations.
  • Traces identify validation, permission, transport, and domain failures separately.

Evidence to keep

Submit the working artifact or decision document described above, the inputs used, and the observed results for every acceptance check. Include one failed attempt and the change you made after investigating it. Label fixture-based outcomes separately from live-system measurements. These artifacts become part of your final portfolio review.

YOUR LEARNING JOURNEY

0 of 118 available lessons completed

Progress saved in this browser. No account needed.
Lab: implement a guarded tool registry | Agentic AI | Android Engineers