Project & context

A connected client works in one project on one branch at a time. These tools choose that context and load what a client should know before doing anything else: the project summary, its conventions, its settings, and the caller’s own review queue.

switch_project

Scope: read

Point this connection at a different Avera project. Every other tool reads and writes in the currently selected project only, so call this before answering a question about a project other than the active one. Only projects covered by this connection's grant can be selected; call it with no arguments to see the active project and the alternatives without changing anything.

Input schema

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "Project key to switch to, e.g. 'VPP'. Omit to report the current selection."
    }
  },
  "required": []
}

switch_branch

Scope: read

Point this connection at a different branch of the active project. Items differ between branches — a requirement on a variant branch may not exist on main, and the same number can carry different content — so a question about a variant or a release line must be answered from that branch. Switching project resets the branch to that project's main. Call with no arguments to list the branches available without changing anything.

Input schema

{
  "type": "object",
  "properties": {
    "branch": {
      "type": "string",
      "description": "Branch key to switch to, e.g. 'main'. Omit to report the current branch and the alternatives."
    }
  },
  "required": []
}

get_project_summary

Scope: read

Return a high-level overview of the current project: name, description, key, and a count of items per item type. Use this when the user asks 'what's in this project?' or to size a broad task before drilling in.

Input schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_conventions

Scope: read

Return this project's AI conventions: the team's own terminology, house style and prior decisions, as markdown. Follow them when answering or authoring — prefer their wording to the generic equivalent. Returns empty when the project has set none.

Input schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_project_settings

Scope: read

Return this project's settings: item numbering (scheme, project prefix, separator, digit padding, per-type or shared sequence, custom pattern), document formatting (whether LiveDoc headings are numbered automatically — if so, never type a number into a heading), the validation-traceability pair (the item type whose items are Validation Requirements and the item type that counts as their test coverage; null when unconfigured), and the default AI model. Read-only: a project administrator changes these on the General settings page. For the project's AI conventions use get_conventions.

Input schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_my_review_queue

Scope: read

Return the current user's work queue for the active project — derived from current state, never from task lists. Use this when the user asks "what's waiting on me?", "what do I need to review/approve/endorse?", or "what of mine is stuck?". Entries: `inbound` (ENDORSE = an endorsement slot this user can fill, including re-reviews of stale verdicts; FIRE = a REVIEW item whose transition this user may fire), each with the item number, transition, and whether a signature is needed; `pendingProposals` = pending AI/change proposals awaiting review in this project.

Input schema

{
  "type": "object",
  "properties": {},
  "required": []
}