These tools are available in the standalone McpServer (stdin/stdout mode). They access the database directly via DMSI_DB_PATH.
dmsi_phase_complete #
Mark the current phase as complete. Available in both the in-process bridge and the standalone MCP server.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
summary | string | Yes | Summary of what was accomplished in this phase |
outcome | string | No | Outcome label (used for AUTO decision routing) |
issues | array | No | Array of QA issue objects (see Section 4 for Issues Object schema) |
output_files | array | No | Array of output file paths produced by this phase |
Example Request
{
"jsonrpc": "2.0",
"method": "dmsi_phase_complete",
"params": {
"summary": "Documentation complete. All 6 documents written and reviewed.",
"outcome": "success",
"output_files": [
"docs/output/README.md",
"docs/output/USER-MANUAL.md"
]
},
"id": 1
}
Example Response
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"success": true,
"message": "Phase marked complete. Workflow advancing."
}
}
dmsi_context #
Get the current project and phase context for the running agent.
Parameters: None
Example Response
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"project_id": "proj-abc123",
"project_name": "User Authentication Feature",
"phase_id": "phase-001",
"phase_name": "Development",
"role": "dev",
"instructions": "Implement user login with JWT...",
"criteria": "All tests pass. No security vulnerabilities.",
"resources": [
{"name": "PRD-v1.md", "path": "/path/to/PRD-v1.md", "type": "reference"}
]
}
}
dmsi_task_list #
List all tasks for the current phase.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
phase_id | string | No | Filter by phase ID (defaults to current phase) |
status | string | No | Filter by status: pending, in_progress, completed, failed |
Example Request
{
"jsonrpc": "2.0",
"method": "dmsi_task_list",
"params": {
"status": "pending"
},
"id": 1
}
Example Response
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"tasks": [
{
"id": "TASK-001",
"title": "Implement JWT token generation",
"status": "pending",
"priority": 1
},
{
"id": "TASK-002",
"title": "Add refresh token endpoint",
"status": "pending",
"priority": 2
}
]
}
}
dmsi_task_update #
Update the status or notes of a task.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
task_id | string | Yes | ID of the task to update |
status | string | No | New status: in_progress, completed, failed |
notes | string | No | Notes to append |
dmsi_phase_list #
List all phases in the current workflow.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | No | Project ID (defaults to current project) |
Example Response
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"phases": [
{"id": "phase-001", "name": "Requirements", "status": "completed", "role": "pm"},
{"id": "phase-002", "name": "Architecture", "status": "completed", "role": "arch"},
{"id": "phase-003", "name": "Development", "status": "running", "role": "dev"},
{"id": "phase-004", "name": "QA Testing", "status": "pending", "role": "qa"}
]
}
}
dmsi_rework #
Request rework on a previously completed phase.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
phase_id | string | Yes | ID of the phase to rework |
reason | string | Yes | Reason for requesting rework |
direction | string | No | FORWARD (reset downstream) or FAILURE (only failure path). Default: FORWARD |
dmsi_log #
Write a message to the agent’s activity log.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Log message |
level | string | No | Log level: INFO, WARN, ERROR (default: INFO) |
dmsi_notify #
Send a notification visible in the Claudius Corp UI.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Notification title |
message | string | Yes | Notification body |
type | string | No | info, warning, error (default: info) |
Example Request
{
"jsonrpc": "2.0",
"method": "dmsi_notify",
"params": {
"title": "Escalation",
"message": "Missing API credentials for OAuth integration. Cannot proceed.",
"type": "error"
},
"id": 8
}
dmsi_escalate #
Escalate an issue to the Executive Consultant (EC) role.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Escalation message |
phase_id | string | No | Phase ID to associate with escalation |
dmsi_memory_query #
Query product-level learning records.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | string | No | Comma-separated tags to filter by |
role | string | No | Filter by agent role |
limit | integer | No | Maximum results (default: 20) |
Example Request
{
"jsonrpc": "2.0",
"method": "dmsi_memory_query",
"params": {
"tags": "testing,security",
"role": "qa"
},
"id": 9
}
dmsi_memory_add #
Add a learning record to product memory.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | Learning content |
tags | string | No | Comma-separated tags |
role | string | No | Agent role that added this learning |
dmsi_approval_request #
Request human approval before proceeding.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | What needs approval and why |
phase_id | string | No | Phase ID |
The phase will pause until the approval is granted or rejected in the Claudius Corp UI.
dmsi_commit #
Commit staged changes to git.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Git commit message |
files | array | No | Specific files to stage (stages all if omitted) |
Example Request
{
"jsonrpc": "2.0",
"method": "dmsi_commit",
"params": {
"message": "[dev] T001: Implement user authentication with JWT",
"files": [
"src/main/java/com/example/AuthService.java",
"src/test/java/com/example/AuthServiceTest.java"
]
},
"id": 10
}
dmsi_status #
Report the current workflow status.
Parameters: None
dmsi_project_info #
Get metadata about the current project.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | No | Project ID (defaults to current project) |
dmsi_settings_read #
Read a setting value from the settings store.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Setting key |
Example Request
{
"jsonrpc": "2.0",
"method": "dmsi_settings_read",
"params": {
"key": "products.root"
},
"id": 11
}
dmsi_settings_write #
Write a setting value to the settings store.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Setting key |
value | string | Yes | Setting value |
dmsi_messages #
Retrieve historical messages from agent logs.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
phase_id | string | No | Filter by phase ID |
limit | integer | No | Maximum messages to return (default: 50) |
since | string | No | ISO 8601 timestamp — only return messages after this time |
dmsi_brief #
Create, read, or list discussion briefs. Briefs are persistent discussion records that survive context compaction and session boundaries.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | One of: create, read, or list |
topic | string | create, read | Topic slug for create; keyword for read (searches titles) |
content | string | create | Markdown content of the brief |
Example — Create a brief
{
"jsonrpc": "2.0",
"method": "dmsi_brief",
"params": {
"action": "create",
"topic": "auth-middleware-rewrite",
"content": "## Key Decisions\n- Replace session tokens with JWTs\n- 30-day refresh window\n\n## Open Questions\n- Token rotation strategy"
},
"id": 1
}Example — Read a brief
{
"jsonrpc": "2.0",
"method": "dmsi_brief",
"params": {
"action": "read",
"topic": "auth"
},
"id": 2
}Example — List all briefs
{
"jsonrpc": "2.0",
"method": "dmsi_brief",
"params": {
"action": "list"
},
"id": 3
}Example Response (list)
{
"jsonrpc": "2.0",
"id": 3,
"result": {
"briefs": [
{"topic": "auth-middleware-rewrite", "created": "2026-04-08T14:30:00Z", "updated": "2026-04-09T09:15:00Z"},
{"topic": "release-planning", "created": "2026-04-07T10:00:00Z", "updated": "2026-04-07T10:00:00Z"}
]
}
}