Skip to main content
Glama

Get the general invitation link

well_get_general_invite_link
Read-only

Return the general invitation link to Well: the link a user forwards so that someone opens their OWN account on Well. It opens the WhatsApp chat with Well, and the person who uses it gets their own workspace, not the user's. Use it when the user asks for a link to invite someone to Well in general ("un lien pour que quelqu'un ouvre un compte sur Well").

It gives no access to any workspace of the user. For a link into the user's own workspace, use well_get_workspace_invite_link. When the user asks for "the invitation link" and does not say which of the two they mean, ask them before any call.

Pass language, the language of the conversation, so the greeting the link carries is in that language.

Input Schema

NameRequiredDescriptionDefault
languageNoThe language of the conversation, for the greeting the link prefills. Defaults to English.
workspace_idNoTarget workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
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.
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.

Output Schema

NameRequiredDescriptionDefault
errorNo
successYes
general_linkNoThe link that opens the WhatsApp chat with Well. A person who uses it gets their own workspace. Give it to the user exactly as returned. Absent when success is false.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / newly_connected / description
      Previous value: -"Tools 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. Start the reply with 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."New value: +"Tools 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."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds non-obvious behavioral context: the link confers no access to the user's workspace, it opens a WhatsApp chat with Well, and the language parameter drives the prefilled greeting. No return format or rate-limit detail, but nothing misleading.

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?

Front-loaded with the core answer, then routing, then the caveat, then the parameter hint — a sensible order. Slightly long for a single-parameter-effect tool, and the inline French quote is illustrative but adds bulk.

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?

An output schema exists, so return values need not be explained. Combined with full schema coverage and annotations, the description supplies everything needed to decide, route, and call correctly — including the disambiguation rule for the near-identical sibling tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description's note on `language` ('so the greeting the link carries is in that language') largely restates the schema's own text, and it says nothing about workspace_id, conversation_id, or workspace_scope beyond what the schema documents.

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 ('Return the general invitation link to Well') and immediately distinguishes the artifact's scope: it opens the recipient's OWN account, not the caller's workspace. The sibling relationship with well_get_workspace_invite_link is made explicit, so an agent can pick correctly without opening either schema.

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 explicit when-to-use ('user asks for a link to invite someone to Well in general'), names the alternative for the other case ('For a link into the user's own workspace, use well_get_workspace_invite_link'), and even prescribes a clarification turn when the request is ambiguous. This is the full when/when-not/alternative triad.

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