Most tools are permission-controlled: they’re hidden from an AI assistant
entirely if that person can’t view them, and rejected at execution time if
the caller can’t
execute them. Only
context_get and knowledge_ask are not
permission-controlled (see their entries below for why).Context
context_get
Returns the authenticated user’s own context — their internal user ID,
organization ID, department ID, name, and email. Not permission-controlled, so it’s
always available; agents should call this first to discover the IDs needed
for every other tool call.
Parameters: none.
Users
users_list
List users with optional filters.
users_get
Get a specific user by ID.
users_update
Update a user’s name and/or email.
users_delete
Delete a user.
Organizations
orgs_update
Update an organization’s name and/or slug. At least one of name or slug
must be provided.
Departments
depts_list
List departments with optional filters.
depts_create
Create a new department.
depts_update
Update a department’s name and/or slug.
depts_delete
Delete a department.
Roles
roles_list
List role templates available in an organization.
roles_assign
Assign a role template to a user.
roles_revoke
Revoke a role template from a user.
Projects
projects_list
List projects in an organization. Requires can_list_projects (org admin).
projects_get
Get full details for a project: phase, department, all members with roles,
and integration config if present.
projects_create
Create a new project. The slug is auto-generated from name; on a slug
conflict a random suffix is appended automatically (up to 3 attempts).
projects_update
Update a project. At least one of name, description, artifactUrl,
phaseId, or departmentId must be provided. Passing null for
description, artifactUrl, or departmentId clears that field.
projects_members_list
List all members of a project with their user details and roles.
projects_phases_list
List available project phases for an organization. Returns org-specific
phases if they exist, otherwise falls back to system phases. Requires
can_list_projects on the organization.
Framework (checklist)
framework_list_categories
List all Engineering Planning Framework categories with their subcategories.
Use this first to understand the framework’s high-level structure.
Parameters: none.
framework_list_items
List checklist items, optionally filtered by category or subcategory. Each
item reports whether a definition (hasDefinition) and artifact template
(hasTemplate) are available.
framework_get_item
Get full details for a single checklist item by slug, including category and
subcategory context and resource URIs (checklist://definitions/<slug>,
checklist://templates/<slug>) for its definition/template.
framework_get_definition
Get the full definition text for a checklist item inline (as opposed to via
the MCP resource protocol). Returns a message if no definition exists.
framework_get_template
Get the full artifact template markdown for a checklist item inline. Returns
a message if no template exists.
Planning
planning_get_status
Get a project’s planning completion status: counts of scoped checklist items
by status (complete, in_progress, not_started, not_applicable) and a
completion percentage. Only counts items explicitly added to the project’s
scope — a new project with nothing scoped returns totalItems: 0.
planning_get_gaps
Get incomplete scoped checklist items for a project (excludes complete and
not_applicable). Optionally restrict to a category, or to categories mapped
to a given phase via Settings → Phase Mapping — when phaseId is passed, the
response includes hasPhaseMapping indicating whether any mapping exists for
that phase.
planning_list_items
List every checklist item in a project’s scope regardless of status. Returns
an empty array if nothing has been scoped yet.
planning_create_item
Add a checklist item to a project’s scope with not_started status. Errors
if the item is already in scope or the slug is unknown.
planning_update_item
Upsert the status of a scoped checklist item — creates the record if it
doesn’t exist, updates it if it does.
planning_get_item_context
Get everything an agent needs to generate an artifact for one checklist
item in one call: full project details, item metadata, current status,
artifact URL, and definition/template content if available. For checklist
items mapped in the Knowledge Base PRD (ADRs, alternative approaches,
runbooks, design rationale, problem-space research), also returns
priorArt — relevant existing Knowledge Base documents to review before
re-deriving the item from scratch. priorArt is null for items with no
Knowledge Base mapping.
Knowledge Base
knowledge_ask
Search the Knowledge Base for prior art relevant to the current planning
task (existing designs, decisions, documented patterns). Proxies to the
Knowledge Base MCP server’s own ask tool, forwarding the caller’s identity
so results are already filtered to what that user is authorized to see.
Degrades gracefully: if the Knowledge Base service is unreachable, returns
available: false with an empty result set instead of failing the call —
treat that as “lookup wasn’t possible,” not “no prior art exists.”