Skip to main content
Glama

Create Connection

createConnection

Create a new user-provided connection (custom MCP server) for the current team. A custom MCP server is registered first with POST /v2/teams/:team_id/integrations/custom, and its id is passed as custom_integration_id; a custom MCP connection without one is refused with 400. OAuth-based integrations (native) require an interactive browser flow — start them with the dedicated OAuth endpoints (/v2/teams/:team_id/connections/oauth/native/:provider/start or /v2/teams/:team_id/connections/oauth/mcp/start) instead of calling this endpoint directly.

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": {
      "name": "<name>",
      "provider": "<provider>",
      "auth_method": "<auth_method>"
    },
    "name": "createConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
typeNocustom_mcp
headersNo
team_idNoDuvo team UUID to operate on. API keys are pinned to a single team — omit this (it falls back to the key's team) or pass that same team; a different team is rejected. OAuth callers, who can span multiple teams, should pass the target team here.
providerYes
server_urlNo
auth_methodYes
custom_integration_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare it is a non-idempotent, non-destructive write. The description adds real behavioral context beyond them: a custom MCP connection without custom_integration_id is rejected with a 400, and OAuth flows require an interactive browser session. It does not describe what the created connection returns or secret-handling behavior for headers.

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?

Two sentences, front-loaded with the core action, then the prerequisite and the routing exclusion. The endpoint paths are long but each carries necessary routing information; nothing is redundant with the title or schema.

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

Completeness3/5

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

For an 8-parameter creation tool with nested objects and no output schema, the description covers the highest-risk decisions (prerequisite registration and OAuth exclusion) but leaves the auth_method/headers combinations unexplained, which is the main remaining ambiguity for a caller.

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

Parameters2/5

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

Schema description coverage is only 13% across 8 parameters, so the description must compensate. It explains custom_integration_id's provenance and the OAuth exclusion around provider/auth_method, but leaves the auth_method enum values (url, apikey, headers, oauth) and the nested headers object (secret vs plaintext) entirely undefined in both schema and description.

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 — creating a user-provided connection (custom MCP server) scoped to the current team — and immediately distinguishes it from OAuth/native integrations that go through a different flow. An agent can tell what this tool creates without opening the 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?

Explicitly routes the agent: OAuth-based native integrations must start via the dedicated /oauth/... endpoints rather than this one, and custom MCP servers must be registered first via POST /v2/teams/:team_id/integrations/custom. Both the when and the when-not are stated with concrete alternatives.

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