[rami-hatoum]

A person's agent calls add_connection; a client that opens links is asked to open the approval page; the person opens it, approves, allows the provider and is sent back, then presses the client's "I'm done, continue". The client retries the call, and the server answered the retry with the answer it had kept before the page was opened: the connection pending, with its link. The agent then told the person to open a link that their approval had already used up.

The answer after the link now says where the connection stands. On the retry the server reads the connection as it is: connected, with no link and words that say nothing is left to open; pending while its link lasts, with the link and the words that say to open it, since the person may have pressed continue without approving; pending with its link gone, with words that say to remove it and add it again; or removed, when the person cancelled on the page, with words that say nothing is connected. Where the client says the person declined to open the page, the words say so and the link is in the answer. The request state keeps what the re-read needs rather than the whole answer; a retry by another caller or in another org is refused as before, and no retry adds a second connection. A client that does not open links gets the answer with the link, unchanged.

The mechanism stays general: beside the link a tool offers, its definition says how it answers the retry after the link, a read that gives the fresh output, so the tool layer knows nothing of connections. The operations package's entry stops exporting types nothing outside the package uses. The MCP reference and the connections guide say what the retry answers, and the OpenAPI document carries connect only while there is a link to open.