Discover and call project tools
Use stable IDs and retrieve each project’s current tool schemas.
Discovery tools
| Tool | Purpose |
|---|---|
| alshitask_organizations | List authorized organizations with IDs, names and effective capabilities. |
| alshitask_projects | List authorized projects, optionally filtered by organization_id. |
| alshitask_tools | Retrieve schemas with explicit organization_id and project_id. |
| alshitask_call | Call a discovered tool with organization_id, project_id, name and arguments. |
Finish pagination
Discovery uses limit and an opaque cursor. Pass next_cursor back as cursor until it is null, keeping other filters consistent. An across-organization page may cover only one organization’s project page. Empty pages may still have a continuation. Treat reported organization failures as incomplete discovery, not as an empty successful result.
Read example
After discovering the project and confirming its current schema, a tool-call argument object looks like this:
{
"organization_id": "ORGANIZATION_UUID",
"project_id": "PROJECT_UUID",
"name": "alshitask_list_tasks",
"arguments": {}
}Replace both placeholders with discovered IDs. Use the actual returned schema for any filters or other tool arguments.
Explicit context
There is no mutable current organization. Every call identifies its organization and project, so concurrent work in separate projects keeps its context. Project services remain authoritative for permissions and tool behavior.