Skip to main content
Glama
LevSky22

nango-mcp-server

by LevSky22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_reconnect_session

Create a reconnect session for an existing connection, enabling users to re-authenticate and restore integration access.

Instructions

Create a Nango reconnect session for an existing connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentYes
connectionIdYes
providerConfigKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / connectionId
      Added value: +{
+  "title": "Connectionid",
+  "type": "string"
+}
    • removedInput schema / properties / connection_id
      Removed value: -{
-  "title": "Connection Id",
-  "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",
-  "connection_id",
-  "provider_config_key"
-]New value: +[
+  "environment",
+  "connectionId",
+  "providerConfigKey"
+]
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / properties / confirmation
      Removed value: -{
-  "default": "",
-  "title": "Confirmation",
-  "type": "string"
-}
  3. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It identifies the operation but does not disclose side effects, whether credentials are invalidated, what a reconnect session actually returns, or any required preconditions. An agent cannot predict the outcome of invoking this tool.

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 front-loaded sentence with no filler or redundancy. It is efficiently structured, though its brevity leaves behavioral and usage gaps that are penalized in other dimensions.

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

Completeness2/5

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

Because there are no annotations, no output schema, and no parameter descriptions, the description needs to provide substantially more context. It tells the agent what the tool does at a high level but not what a reconnect session is, how it is used afterward, what the response contains, or how it differs operationally from sibling session tools.

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 provides no additional meaning for environment, connectionId, or providerConfigKey. The parameter names are somewhat self-explanatory, but no formats, defaults, constraints, or relationships are described, and the description does not compensate for the missing schema documentation.

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 ('Create') and resource ('Nango reconnect session'), with the qualifier 'for an existing connection.' This clearly distinguishes it from sibling tools like create_connect_session or create_standard_connect_session, whose purpose is creating new sessions.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, nor does it name alternatives. 'For an existing connection' implies a distinction from new-connection flows, but the agent is not told when to prefer reconnect over create_connect_session or refresh_connection_credentials.

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