Skip to main content
Glama

Decline reconnect notices

well_decline_connector_reconnect
Idempotent

Record a person's no to the reconnect notice for one exact connection. Call this only after the person says they do not want that connection back. Use workspace_connector_id from the notice, never a connector slug; two installs of the same connector are separate choices. Only the notice recipient can record the choice. A successful call stops later reconnect notices for this connection until the person reconnects it in Well. It sends no message and reconnects nothing.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.
workspace_connector_idYesThe exact connection id carried by the reconnect notice.

Output Schema

NameRequiredDescriptionDefault
errorNo
successYes
recordedYes
connector_nameNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
workspace_connector_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by stating the effect (future reconnect reminders stop until the person reconnects in Well) and the limits ("It sends no message and reconnects nothing"), plus permission scope. The only blemish is calling the call "this read" in the workspace paragraph while annotations mark readOnlyHint=false, but the surrounding text and the idempotency_key wording ("a retried write") make it clear this is a write, so it is a wording slip rather than a real contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition opens with the core action and the safety precondition, then moves to side effects and workspace selection. It is compact, and the second paragraph on workspace_id is slightly longer than needed given that the schema already covers the same rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation and consent-recording tool, the definition covers the precondition, the exact identifier to use, the side effect, and which calls do not happen. An output schema and annotations are already present, so nothing essential about calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3. The description earns more by explaining that workspace_connector_id must come from the notice rather than a slug, that two installs of the same connector are separate choices, and by spelling out the multi-workspace rule for workspace_id before the schema is read.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Record a person's no to the reconnect notice for one exact connection." It is clearly distinguished from nearby siblings such as well_mark_connects_told and well_retarget_connectors by naming the exact object (a reconnect notice for one connection) and the exact effect (recording a refusal).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ("Call this only after the person says they do not want that connection back"), an identity constraint (only the notice recipient may record it), and a data source rule (use workspace_connector_id from the notice, never a connector slug). It also tells the agent when no workspace lookup is needed versus when workspace_id must be passed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources