AppWorld task procedure
API access
apisis already injected into the persistent AppWorld shell. Do not writeimport apisorfrom apis import ...; the shell rejects those imports.- Call APIs directly with
apis.<app_name>.<api_name>(...). - Always wrap calls in
print(...)so the returned value is visible in tool output.
Discovery
- Start with
print(apis.api_docs.show_app_descriptions())to see the available apps. - For the relevant app, run
print(apis.api_docs.show_api_descriptions(app_name='<app>')). - For each API you plan to use, run
print(apis.api_docs.show_api_doc(app_name='<app>', api_name='<api>'))and follow the documented parameter names and required arguments exactly.
Execution
- Prefer keyword arguments exactly as shown in the API docs.
- Verify each action by reading back the affected objects/collections before moving on.
- If a call raises an error, re-read the API doc rather than guessing argument names or shapes.
Completion
- When the requested information has been obtained or the requested world changes are done, call the documented supervisor completion API and print its result.
- Do not read grading, ground-truth, or benchmark files.