azurenoops / azurenoops/spin_agent

[BUG] [MCP/Kanban] - Kanban board / remediation task intents return 'An error occurred' with success:true — zero tools executed, feature completely inaccessible via API

Open
#576 0 comments 0 reactions 1 assignee Claimed by @jrspinella View on GitHub
agent:oracle area:rmf bug priority:high
Dominant language
C#
Stars
3
Forks
1
Avg merge
18h 9m
Merged PRs (30d)
43

Description

## Bug Description

All Kanban/remediation board intents via `/mcp/chat` return `"**Error**: An error occurred."` with `success: true` and **zero tools executed**. This is a contradictory response (success=true alongside an error message) and means the Kanban/remediation features are completely inaccessible via the MCP API.

## Steps to Reproduce

```bash
BASE="https://ca-ato-copilot-mcp-v2.blackwater-9393aa1a.centralus.azurecontainerapps.io"

# Attempt 1: Show kanban board with systemId
curl -s -X POST -H 'Content-Type: application/json' \
-d '{"message":"Show kanban board", "systemId":"92afdc15-bc6f-4648-8073-ad6af396cf97"}' \
"$BASE/mcp/chat"

# Attempt 2: Show Kanban board for Coastal Watch
curl -s -X POST -H 'Content-Type: application/json' \
-d '{"message":"Show me the Kanban board for Coastal Watch remediation tasks"}' \
"$BASE/mcp/chat"

# Attempt 3: Kanban task list (suggested action from the API itself)
curl -s -X POST -H 'Content-Type: application/json' \
-d '{"message":"Show kanban board"}' "$BASE/mcp/chat"
```

## Expected Behavior

The agent dispatches to `kanban_task_list` and returns remediation task records for the specified system (or prompts for system selection).

## Actual Behavior

```json
{
"success": true,
"response": "**Error**: An error occurred.",
"agentUsed": "Compliance Agent",
"intentType": "compliance",
"processingTimeMs": 51,
"toolsExecuted": [],
"errors": []
}
```

Contradictory state: `success: true` but error message in response. No tool is called. The suggested follow-up action (`"Show Kanban Board"`) itself produces the same error when used.

## Note

The `kanban_task_list` tool is available in `GET /mcp/tools` and has the required parameters (`board_id` or system context). The intent routing appears to throw before tool dispatch.

## Browser/Environment

Azure Container Apps MCP API
Endpoint: POST /mcp/chat
Date: 2026-06-30T12:15:00Z
Sweep: Automated QA sweep

## Playwright Test Code

```typescript
test('[MCP] Kanban board intent dispatches to kanban_task_list', async ({ request }) => {
const response = await request.post('/mcp/chat', {
data: {
message: 'Show kanban board',
systemId: '92afdc15-bc6f-4648-8073-ad6af396cf97'
}
});
const body = await response.json();
expect(body.success).toBe(true);
expect(body.response).not.toContain('An error occurred');
expect(body.toolsExecuted.length).toBeGreaterThan(0);
});
```

*Filed by Oracle — Automated 4-hour QA Sweep 2026-06-30T12:15:00Z*

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.