Skip to main content
Glama

Invoke connector tool

well_invoke_connector_tool
Destructive

Run one tool on a connected provider's own MCP server, on behalf of this workspace's connection: an action the user asked to take there (create a record in Attio), or a read of content Well does not sync (a page in a docs tool, a note in a CRM, a file the user pasted a link to).

It is NOT a way to read financial data: Well already syncs invoices, transactions, accounts and the accounting graph from every connected provider — read those with well_query_records instead of calling a provider's own list/read tools. The one exception is a report the accounting tool builds and Well does not sync, such as a QuickBooks or Xero profit and loss or balance sheet: read that report with this tool, and state its lines as returned.

WORKFLOW:

  1. well_list_connectors() → pick the connected provider (connection_status "enabled" or "processing": a connection whose sync was started still serves its tools) and read its workspace_connector_id directly off the row. A workspace_connector_id the user pasted is fine to use as-is: it is resolved inside this workspace, and an id that does not belong here fails server-side.

  2. well_list_connector_tools({ workspace_connector_id }) → the live tool names + input schemas that connection actually exposes right now.

  3. well_invoke_connector_tool({ workspace_connector_id, tool: "<one of the names from step 2>", args: { ... } }).

Only works on connectors that expose an MCP server (e.g. Attio, Notion, Linear) and whose connection is enabled or processing (a sync was started on it). A read-only tool runs at once. A write tool that Well reviewed for that provider waits for the user's approval in Well: the first call runs nothing and returns status "pending_confirmation" with a confirmation_request_id. Tell the user to approve the request in Well, then call again with the same arguments and that confirmation_request_id. A confirmation_request_id runs one call only: never reuse it, and never pass one the user did not approve. Any other write tool is refused: tell the user that the action is not available and do not retry it. Returns the provider's tool result, or { success: false, error } if the tool failed / is not granted.

Input Schema

NameRequiredDescriptionDefault
argsNoArguments object passed straight to the provider tool. Omit if the tool takes none.
toolYesThe provider tool name to run (one of the connector's available_tools).
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 connected provider's workspace_connector_id (from well_list_connectors).
confirmation_request_idNoThe confirmation_request_id a pending_confirmation result returned, once the user approved it in Well. Omit on the first call.

Output Schema

NameRequiredDescriptionDefault
toolNo
errorNo
resultNo
statusNo
successYes
always_askNo
error_codeNo
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.
untrusted_content_noteNo
confirmation_request_idNo

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. Changed2 schema fields changed
    • addedInput schema / properties / workspace_scope
      Added value: +{
      +  "description": "Restrict 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.",
      +  "enum": [
      +    "family"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / always_ask / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "payment",
      -      "paid_plan_change",
      -      "bank_details",
      -      "password",
      -      "contact_consent"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "payment",
      +      "paid_plan_change",
      +      "bank_details",
      +      "password",
      +      "contact_consent",
      +      "credit_spend"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed2 schema fields changed
    • changedOutput schema / properties / always_ask / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "payment",
      -      "paid_plan_change",
      -      "bank_details",
      -      "password"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "payment",
      +      "paid_plan_change",
      +      "bank_details",
      +      "password",
      +      "contact_consent"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / newly_connected
      Added value: +{
      +  "description": "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.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "service_id": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "service_id"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. Changed5 schema fields changed
    • addedInput schema / properties / confirmation_request_id
      Added value: +{
      +  "description": "The confirmation_request_id a pending_confirmation result returned, once the user approved it in Well. Omit on the first call.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / always_ask
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "payment",
      +        "paid_plan_change",
      +        "bank_details",
      +        "password"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / confirmation_request_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / status
      Added value: +{
      +  "const": "pending_confirmation",
      +  "type": "string"
      +}
    • addedOutput schema / properties / untrusted_content_note
      Added value: +{
      +  "type": "string"
      +}
  5. Changed4 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id_note
      Added value: +{
      +  "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id_source
      Added value: +{
      +  "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
      +  "enum": [
      +    "host_meta",
      +    "argument",
      +    "minted"
      +  ],
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Target workspace. Omit to use the only authorized workspace, or (for read tools) to query all authorized workspaces grouped by workspace. Required for write tools when the token authorizes more than one workspace."New value: +"Target 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."
  7. Changed1 schema field changed
    • changedInput schema / properties / workspace_connector_id / description
      Previous value: -"The connected provider's workspace_connector_id (from well_query_records on workspace_connectors)."New value: +"The connected provider's workspace_connector_id (from well_list_connectors)."
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Far exceeds the annotations (readOnly=false, destructive=true, openWorld=true). It discloses the pending_confirmation approval flow, that the first write call executes nothing, that confirmation_request_id is single-use and must not be reused or fabricated, that unreviewed write tools are refused without retry, and the { success: false, error } failure shape. That is exactly the behavioral context an agent needs for a destructive external call.

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?

Purpose is front-loaded in sentence one, followed by the negative scope, then a numbered workflow, then the write-approval rules — a sensible ordering. It is long and uses dense em-dash constructions that could be tightened, but nearly every sentence carries load-bearing information for a tool with an approval gate.

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 an 8-parameter, open-world, destructive tool with a nested args object and an output schema, the description covers the full call path: discovery, tool enumeration, invocation, approval handling, error/refusal behavior, and return shape. Nothing an agent needs to call this safely 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 is 3; the description nevertheless adds procedural semantics the schema lacks — that 'tool' must come from the live list in step 2, that 'args' is passed straight through (and omitted when empty), and the full lifecycle of confirmation_request_id. It is not exhaustive per-parameter prose, but it materially informs correct invocation.

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?

The opening sentence states a specific verb and resource ('Run one tool on a connected provider's own MCP server') and immediately draws the boundary against well_query_records. An agent can distinguish this from the many sibling read/write tools without opening a 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?

It gives explicit when-to-use (user-requested provider action, unsynced reads, accounting reports Well does not sync), explicit when-NOT-to-use (financial data already synced → well_query_records), and named alternatives in the sibling set. It also lays out a three-step workflow that routes through well_list_connectors and well_list_connector_tools first.

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