Skip to main content
Glama
LevSky22

nango-mcp-server

by LevSky22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_standard_connect_session

Create a Connect session to start an authentication flow and receive the post-auth finalization contract for completing the integration connection.

Instructions

Create a Connect session and return its post-auth finalization contract.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
purposeYes
ownerKindYes
principalYes
displayNameNo
environmentYes
oauthAppOwnerNo
organizationIdNo
providerConfigKeyYes
integrationsConfigDefaultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv2.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / displayName
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Displayname"
+}
    • removedInput schema / properties / display_name
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Display Name"
-}
    • removedInput schema / properties / email / default
      Removed value: -null
    • addedInput schema / properties / integrationsConfigDefaults
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Integrationsconfigdefaults"
+}
    • removedInput schema / properties / integrations_config_defaults
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Integrations Config Defaults"
-}
    • addedInput schema / properties / oauthAppOwner
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Oauthappowner"
+}
    • removedInput schema / properties / oauth_app_owner
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Oauth App Owner"
-}
    • addedInput schema / properties / organizationId
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Organizationid"
+}
    • removedInput schema / properties / organization_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Organization Id"
-}
    • addedInput schema / properties / ownerKind
      Added value: +{
+  "title": "Ownerkind",
+  "type": "string"
+}
    • removedInput schema / properties / owner_kind
      Removed value: -{
-  "title": "Owner Kind",
-  "type": "string"
-}
    • addedInput schema / properties / providerConfigKey
      Added value: +{
+  "title": "Providerconfigkey",
+  "type": "string"
+}
    • removedInput schema / properties / provider_config_key
      Removed value: -{
-  "title": "Provider Config Key",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "environment",
-  "provider_config_key",
-  "principal",
-  "owner_kind",
-  "purpose"
-]New value: +[
+  "environment",
+  "providerConfigKey",
+  "principal",
+  "ownerKind",
+  "purpose"
+]
  2. Changed2 schema fields changedv1.0.0
    • removedInput schema / properties / confirmation
      Removed value: -{
-  "default": "",
-  "title": "Confirmation",
-  "type": "string"
-}
    • addedInput schema / properties / oauth_app_owner
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Oauth App Owner"
+}
  3. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a session is created and a contract is returned, but does not explain side effects, authentication requirements, error behavior, or what the 'post-auth finalization contract' actually entails. For a creation tool this is insufficient.

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 description is a single sentence with no filler, and the action is front-loaded. However, the phrase 'post-auth finalization contract' is jargon that is not explained, and the extreme brevity sacrifices essential detail, making it concise but not optimally clear.

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

Completeness1/5

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

With 10 parameters, no annotations, and no output schema, the description must compensate heavily but does not. It omits explanations of required parameters, usage context, return contract details, and any preconditions. The tool is severely under-specified for an agent to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any of the 10 parameters, such as environment, providerConfigKey, principal, or purpose. The agent is left entirely to infer parameter meaning from names alone, which is especially problematic for ambiguous fields like ownerKind and integrationsConfigDefaults.

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

Purpose4/5

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

The description states a clear verb ('Create') and resource ('Connect session'), and mentions the return of a 'post-auth finalization contract,' which adds specificity. However, it does not distinguish this tool from sibling tools like create_connect_session or create_reconnect_session, so the agent cannot tell which session creation variant to use.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as create_connect_session or create_reconnect_session. The description gives no context about typical scenarios, prerequisites, or conditions under which this standard connect session is preferred.

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

Deploy Server

Other Tools