Tool catalog

Ask a question and receive an evidence-backed Operational Delivery Brief assembled live from Project Health and Project Risk authorities. Project IDs target one project; engagement IDs compose caller-visible projects; no ID means portfolio scope. Read-only. It does NOT retrieve uploaded documents, transcripts, decisions, assumptions, or requirements, and performs no semantic search.

Search the Engagement Knowledge Corpus: ranked full-text retrieval of evidence spans from ingested Context Sources bound to an authorized project or engagement. Returns exact passages with provenance (source, page/paragraph/section, provenance quality, timestamps) — evidence, not a synthesized answer. It does NOT return project health or risks, does NOT synthesize decisions, and performs NO semantic/vector search (PostgreSQL full-text only). Project queries search directly-bound sources; engagement queries fan out to caller-visible child projects (direct engagement-bound sources are not yet supported). Read-only. This is the legacy Knowledge-only tool; for cross-domain Context Platform search across evidence, adopted definitions, and decisions in one call, use the platform-native search_unified_context tool.

Read Context Engine availability, package/provider counts, freshness posture, supported capabilities, and recent packages.

List governed context packages with evidence coverage, provenance, freshness, and provider attribution.

Retrieve one governed context package with canonical source reference, provenance, freshness, and coverage.

Search persisted context contributions without invoking arbitrary model execution.

Read policy-safe evidence references and provenance without exposing raw source bodies.

Inspect provider capabilities, contribution counts, coverage, freshness, and authority boundaries.

Read the caller’s daily focus package with an evidence-backed summary, attention items, related entities, coverage, and provenance.

Record an explicit resolve, dismiss, or snooze action for a Today & My Work attention item and emit the matching webhook event.

List the workspace’s projects (engagements) with client name, status, and last-updated time. Useful to enumerate work or resolve a project name to its id.

A one-call health snapshot for a project: delivery status, alerts, phase and milestone progress, workstream states, and directional financial/staffing signals (governed by your permissions).

Record a confirmed acknowledgement for one advisory Project Health alert and emit project_health.alert_acknowledged.

List visible canonical projects/engagements through the governed public API.

Retrieve one visible canonical project/engagement identity record.

Create one canonical project/engagement identity through a confirmed, idempotent command.

Update bounded project identity and relationship fields.

Run one explicit project lifecycle status command.

Archive one project through the explicit project lifecycle command path.

List governed project membership rows for one visible project.

Add or upsert one project member through a confirmed command.

Update one project member role through a confirmed command.

Remove one project member through a confirmed command.

Read bounded public project settings.

Update bounded project settings through a confirmed command.

Read one governed estimate, or list estimates for a project, with scope, effort, role demand, risks, timeline, provenance, and immutable-baseline identity.

Persist a reviewable estimate change proposal without mutating canonical estimate, staffing, schedule, or baseline state.

Submit a confirmed draft proposal for human baseline review. The MCP tool cannot freeze, approve, sign, or supersede a baseline.

Report on a project’s active (or specified) sprint: goal, totals, work items by status, blocked items, and spillover risk.

Read a project sprint-planning context and readiness score as a read-only projection.

Generate citation-gated planning intents for review. Proposal-only; it does not apply a plan or move work.

Read governed delivery milestones and workstreams for one project without moving execution coordinates.

List Delivery-owned milestones for one project with scoped work-item ids.

Retrieve one governed Delivery milestone.

List project workstreams through the execution read provider. Read-only in this slice.

Run one confirmed governed milestone status command.

Run one explicit milestone target-date command; does not resize phases or move work.

Run one explicit milestone progress command for completion percentage and/or projected date.

Read canonical DigitalStack work items using board-safe filters such as team, sprint, parent, assignee, and status bucket. Use this to find the right work item before drilling in or running Work Item Enhance.

Read the canonical DigitalStack work-item board grouped by status bucket. This is a read-only projection over Execute work items and does not move cards or mutate workflow state.

Read one source-aware Execute work item through the governed public Work Items API. Jira-backed reads hydrate authoritative description, discussion, people, hierarchy, and relationships without asking the model to infer missing facts.

Read transition history for one canonical work item without changing status, ranking, or board placement.

Inspect the current version, allowed transitions, editable fields, and supported commands before an agent proposes a work-item operation.

Add an attributable comment after explicit confirmation. If the work item is Jira-backed, DigitalStack validates and passes the comment through to Jira.

Apply one allowed Execute flow-state transition after confirmation. Jira-backed work items pass the mapped transition through to Jira.

Assign, reassign, or unassign a work item after confirmation, with Jira pass-through for Jira-backed work items.

Set or clear start, due, target, sprint, or ordering fields through the scheduling command boundary. Jira due-date writeback is supported when mapped.

Set or clear work-item points after confirmation. Jira-backed estimates require a configured story-points field mapping.

Add, remove, or replace normalized labels after confirmation. Jira-backed labels are passed through to Jira.

Create a dependency or relationship after validating target visibility and cycles.

Raise, update, transition, or resolve a blocker linked to a work item after confirmation.

Pin, reprioritize, snooze, annotate, or clear a work item in focus views without mutating authoritative schedule or staffing.

Detail on a single work item: description excerpt, status, assignee, parent/children, open blockers, and recent status transitions.

List proposal-first enhancement runs by target work item and state.

Create a proposal-first Work Item Enhance run with selected actions such as requirements, description, design, implementation plan, acceptance criteria, test plan, estimate, and risk check.

Retrieve one Work Item Enhance run with target, requested actions, drafts, artifacts, allowed actions, and apply history.

Read the operation-style status view for a Work Item Enhance run.

Run any allowlisted action on an existing enhancement run, such as code context, implementation plan, acceptance criteria, test plan, estimate, or risk check.

Run the requirements action on an existing enhancement run and return generated field-level drafts for review.

Run the description action on an existing enhancement run and return a clearer work-item description draft.

Run the design action and return an advisory design artifact without changing the work item.

Read generated code-context artifacts for a Work Item Enhance run: likely files, likely tests, implementation areas, missing context, and guardrails.

List generated field-level drafts for a run, optionally filtered by action, field, or apply eligibility.

List generated review artifacts for a run, optionally filtered by artifact type.

Read selected drafts and prepare the field-level apply preview. The actual apply remains an explicit confirmed REST command.

Apply selected reviewed drafts to the canonical work item using explicit confirmation, optimistic target versioning, and idempotency.

Aggregated risk picture for a project: delivery alerts, client-dependency blocks, and open risk/gap/request issues, with a coverage block.

List the caller’s self-scoped canonical time entries by date range, project, status, and limit.

Read one self-scoped canonical time entry.

Update one editable self-scoped time entry with optimistic versioning and explicit confirmation.

Void one editable self-scoped time entry with optimistic versioning and explicit confirmation.

Read the caller’s current canonical timer, if any.

Read the caller's privacy-safe work day, including entries, attributed sessions, conflicts, gaps, timer, draft, totals, and submission state.

Persist a proposal from fully attributed DigitalStack work sessions. Conflicts and unresolved evidence remain gaps; no actual time is created.

Apply a reviewed proposal to canonical entries with optimistic versioning, idempotency, and explicit confirmation.

Record one user-supplied time entry. It cannot silently convert inferred activity into an actual.

Start the caller's single canonical timer for an explicit target.

Pause the caller’s active canonical timer with optimistic versioning and explicit confirmation.

Resume the caller’s paused canonical timer with optimistic versioning and explicit confirmation.

Atomically stop the active timer and create exactly one draft entry.

Discard the caller’s active or paused canonical timer without creating a time entry.

Validate and submit one reviewed work day into the canonical approval lifecycle.

Recall one submitted work day while policy permits, using explicit confirmation.

List eligible team time approvals for the authenticated reviewer.

Approve or reject an eligible submission as the authenticated human approver.

List governed provider time import runs for authorized administrators.

Create a governed provider time import run with date range, idempotency, and explicit confirmation.

List governed provider reconciliation findings without exposing raw provider payloads or financial rates.

Run a reconciliation scan for a date range. It records findings only and does not mutate approved entries.

Resolve one reconciliation finding through DigitalStack policy with explicit confirmation.