qase_project_context
Gather all project metadata in one request: project details, suites, milestones, environments, custom fields, and users. Start here to avoid multiple API calls.
Instructions
Get full project context in one call: project details, suites tree, milestones, environments, custom fields, and users. Cached for 5 minutes. Use this as the first call when starting work with a project — it seeds all the metadata the LLM needs without making 6 separate list calls. Each collection returns its first 100 entities by default; the coverage field reports { total, loaded, truncated } per collection, so check it before assuming a list is complete. Pass full: true to page through everything.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Project code (2-10 uppercase letters, numbers, or underscores) | |
| full | No | Page through every suite, milestone, environment, custom field, and user instead of fetching only the first 100 of each (default: false). Use this when a collection is reported as truncated and you need the complete set — it costs one API call per 100 entities and can return thousands of items, so prefer the targeted list tools or qql_search when you only need a subset. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| users | No | Team members list | |
| suites | Yes | Suites list with entities array | |
| project | Yes | Project details | |
| coverage | Yes | Per-collection completeness: each of suites, milestones, environments, custom_fields, and users maps to { total, loaded, truncated }. When truncated is true the list holds only the first `loaded` of `total` entities — re-call with full: true for the rest. | |
| milestones | Yes | Milestones list | |
| environments | Yes | Environments list | |
| custom_fields | No | Custom fields list |