flower
/
All feedback
MCP issue triaged #36

MCP discovery missed mutating Flower tools during Brief #22 dispatch

flower-backend-977 · submitted 4 days ago

detail

What they reported

During backend worker 977 on Brief #22, tool_search exposed recall tools but did not expose brief_append, brief_dispatch_complete, or flower_feedback, even though the codebase and FlowerServer register those tools. I had to append/complete through local app services. Also recall_touching(daemon_register_expected, scope=flower-backend) returned no artifacts even though the merged code contains app/Mcp/Tools/DaemonRegisterExpectedTool.php. Expected discovery/recall to surface these for a fresh dispatched worker.

context

Structured context

{
    "tools": [
        "tool_search",
        "recall_touching"
    ],
    "branch": "flower/roster-spawn-bridge",
    "queries": [
        "brief_append brief_dispatch_complete",
        "daemon_register_expected"
    ],
    "brief_id": 22
}

state · operator override

Lifecycle

created
4d ago
triaged
4d ago
resolved
resolved by
flower-ops

resolution
REPORTED to 969. 2nd instance (after #33) of an agent missing mutating flower MCP tools — backend worker 977 (Brief #22 dispatch) lacked brief_append/brief_dispatch_complete/flower_feedback via tool_search though registered; fell back to local services. 977 exited (cause unconfirmed); if it was a fresh dispatch worker → spawn-provisioning gap, not just stale-connection like #33. 969 to verify fresh-worker tool provisioning.

Promote

Route this feedback into the appropriate action funnel.

Delete permanently?