MCP Tools

Resolve Tool

Tool	Required scope	Purpose
resolve	mcp:resolve	Answer open-ended project routing and responsibility questions.

resolve accepts query, optional project_id, and optional mode (test or live). Use it when the user asks who should handle a task, who to contact, which participant is responsible, or who can act through a delegation.

Project Tools

Tool	Required scope	Purpose
list_projects	mcp:projects:read	Return visible non-deleted projects.
get_project	mcp:projects:read	Return one visible project.
create_project	mcp:projects:write	Create a project and owner membership.
update_project	mcp:projects:write	Update project fields and access.
delete_project	mcp:projects:write	Soft-delete a project.

Project reads follow each project’s status and read_access_mode. live projects use the configured read access mode. draft, test, and archived projects are visible only to admins and project owners. Project writes still require admin access or an owner row. status: "test" projects can be used by resolve only with explicit project_id, mode: "test", and admin or project-owner access.

Participant Tools

Tool	Required scope	Purpose
list_participants	mcp:participants:read	Return visible non-deleted participants.
get_participant	mcp:participants:read	Return one visible participant.
search_directory_records	mcp:participants:read	Search cached directory users and groups.
list_participant_members	mcp:participants:read	List directory users/groups on a participant.
create_participant	mcp:participants:write	Create a participant in a manageable project.
update_participant	mcp:participants:write	Update participant fields, labels, metadata.
add_participant_member	mcp:participants:write	Add a directory user or group to a participant.
remove_participant_member	mcp:participants:write	Remove a directory user or group.
delete_participant	mcp:participants:write	Soft-delete a participant.

Resolve Request History Tools

Tool	Required scope	Purpose
list_resolve_requests	mcp:resolve-requests:read	Return compact visible resolve request history.
get_resolve_request	mcp:resolve-requests:read	Return one visible resolve request with detail.

Label Tools

Tool	Required scope	Purpose
list_labels	mcp:labels:read	Return labels and usage counts.
get_label	mcp:labels:read	Return one label.
create_label	mcp:labels:write	Create a label.
update_label	mcp:labels:write	Update label name or color.
delete_label	mcp:labels:write	Delete a label when allowed.

Label read tools require an active authenticated owner identity. Label mutation tools also require admin or effective project-owner authorization. Non-admin project owners can delete only labels they created, and only when every participant or resolve-request usage is in projects they own.

Delegation Tools

Tool	Required scope	Purpose
list_delegations	mcp:delegations:read	Return visible delegations.
get_delegation	mcp:delegations:read	Return one visible delegation.
create_delegation	mcp:delegations:write	Create a participant delegation.
update_delegation	mcp:delegations:write	Update a delegation.
revoke_delegation	mcp:delegations:write	Revoke a delegation.

List Tool Filters

List and search tools accept a limit from 1 to 100.

list_projects accepts:

{
  "query": "helios vendor",
  "limit": 10
}

query searches project name and description.

search_directory_records accepts:

{
  "query": "ethan wright",
  "type": "user",
  "limit": 10
}

type accepts all, user, or group. query searches cached directory record id, name, email, and description. This tool does not search upstream connectors live.

list_participant_members accepts:

{
  "participant_id": "part_...",
  "query": "ethan",
  "type": "user",
  "limit": 10
}

type accepts all, user, or group. The tool returns direct directory users and groups associated with the participant.

list_participants accepts optional filters:

{
  "query": "finance approvers",
  "limit": 10,
  "project_ids": ["proj_..."],
  "labels": ["Finance", "Vendor"],
  "metadata": [{ "key": "approval_limit_eur", "operator": "gte", "value": 75000 }]
}

Filter groups combine with AND semantics except project_ids, which uses OR semantics. Label matching is case-insensitive by name and exact by ID. Metadata keys must be snake_case. Ordered metadata operators support numeric and date-time metadata.

list_labels accepts:

{
  "query": "finance",
  "limit": 20
}

query searches label name.

list_delegations accepts:

{
  "status": "active",
  "scope": "participant",
  "project_id": "proj_...",
  "participant_id": "part_...",
  "delegator_user_id": "drec_...",
  "delegate_user_id": "drec_...",
  "limit": 25
}

status accepts active, expired, revoked, or upcoming. scope accepts all_participants or participant.

list_resolve_requests accepts:

{
  "project_id": "proj_...",
  "actor_id": "idn_...",
  "resolution_status": "success",
  "created_after": "2026-05-01T00:00:00Z",
  "created_before": "2026-06-01T00:00:00Z",
  "query": "Helios renewal",
  "limit": 25
}

resolution_status accepts success, not_found, out_of_scope, or error. actor_id is the Roster identity id of the authenticated requester who created the Resolve request, for example the user who signed in through OAuth or the identity behind a Roster API key. It is not a directory user id; directory users use drec_... ids in membership and delegation tools. Omit actor_id unless you are filtering history to a specific requester. query searches the original Resolve request text.

Participant reads follow the same project read access rules. Participant writes still require admin access or project ownership.