Skip to main content
Glama

Connect a workspace integration

connect_integration
Read-onlyIdempotent

Return a browser URL to connect GitHub, Linear, Slack or your Telegram account. GitHub, Linear and Slack require a workspace admin or owner. Does not start OAuth or accept secrets; give the URL to the user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "integration": "<integration>"
    },
    "name": "connect_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrationYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / integration / enum
      Previous value: -[
      -  "github",
      -  "linear",
      -  "slack",
      -  "telegram",
      -  "buzz"
      -]New value: +[
      +  "github",
      +  "linear",
      +  "slack",
      +  "telegram"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / integration / enum
      Previous value: -[
      -  "github",
      -  "linear",
      -  "slack",
      -  "telegram"
      -]New value: +[
      +  "github",
      +  "linear",
      +  "slack",
      +  "telegram",
      +  "buzz"
      +]
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds context those annotations cannot express: which integrations need elevated workspace roles, that the call produces a URL rather than performing the connection, and that secrets must never be passed. URL lifetime or whether the link is single-use is not disclosed.

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

Conciseness5/5

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

Three tight sentences: what it returns, who can use it, and what it explicitly does not do. The most decision-relevant fact (it returns a URL for the user) is front-loaded with zero filler.

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

Completeness4/5

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

For a two-parameter read-only tool with no output schema, this covers purpose, permissions and downstream handling of the result. Minor gaps remain around URL expiration or reuse, but nothing critical to 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 50%: workspace_id is documented ('from whoami') but the integration enum is undescribed. The description compensates by enumerating the valid providers and flagging that three are workspace-scoped and admin-gated while Telegram is a personal account, which is meaningful semantics beyond the raw enum.

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 deliverable ('Return a browser URL') plus the exact resource set (GitHub, Linear, Slack, Telegram), which distinguishes it from siblings like connect_subscription and billing_portal. An agent can tell immediately what it gets back and for which providers.

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

Usage Guidelines4/5

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

Gives real preconditions ('GitHub, Linear and Slack require a workspace admin or owner') and an explicit negative constraint ('does not start OAuth or accept secrets; give the URL to the user'), which steers the agent's follow-up behavior. It stops short of naming an alternative tool for cases where this one is inappropriate.

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