Skip to content

mcp: whats_waiting tells agents when to call it; no duplicated description - #1545

Draft
DmitriyG228 wants to merge 1 commit into
t27-onboarding-queuefrom
mcp-whats-waiting-description
Draft

mcp: whats_waiting tells agents when to call it; no duplicated description#1545
DmitriyG228 wants to merge 1 commit into
t27-onboarding-queuefrom
mcp-whats-waiting-description

Conversation

@DmitriyG228

Copy link
Copy Markdown
Member

The whats_waiting tool description served to agents was the flows-api queue_waiting docstring — ~250 words on X-User-Id vs ?subject= precedence, operator keys, 403/400 shapes and VEXA_FLOWS_TIMELINE_KEY — emitted twice, back to back, and it never said WHEN to call. Ten ordinary sessions with the tools loaded never called it.

The route now carries an explicit agent-facing summary and no docstring; the operator mechanics move to a comment beside it. register.py published bt.description as both summary and description, and fastapi_mcp concatenates the two — hence the doubling; it now sets one.

Tests: flows 518 passed (+7); MCP 245 passed.

…ption

Signed-off-by: DmitriyG228 <2280905@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant