[Zernio-Elean]

Why

The Support Assistant (POST /v1/support/runs) already reaches the MCP as generated tools, but the generated ask tool is unsafe for agents: no Idempotency-Key (a client retry bills a second run), no wait for the async answer, and its description is cut before the pricing, so an agent never learns it is paid.

What

• Hand-written async support_ask: starts the run with an Idempotency-Key derived from the arguments (a re-call replays the same run instead of billing twice), waits up to wait_seconds (45 by default, max 120) and returns the run, or a next hint to poll.
• max_cost_usd defaults to 1.0; the description opens with PAID and says when to use it.
• Error hints the agent can act on: OAuth connectors and restricted keys cannot use it, a run already in progress, a duplicate still submitting, rate or spend limit, network errors (retrying is safe).
• askSupportQuestion added to SKIP_OPERATIONS, so support_ask is the only paid entry point; support_ask and support_assistant_get_support_answer are pinned.
• Listed under "Support" in the tools reference.

Follow-ups

• Add a request_id param once zernio-dev/Schedule-Posts-API#5494 is deployed (it is merged).
• Release: the next regenerate run on develop bumps and publishes to PyPI; check which branch Railway deploys for the hosted MCP.