nango-mcp-server

Overview Schema Source Related Servers Discussions Admin

build_connection_convention

Generate a connection_id, tags, and metadata for a managed connection using environment, provider, principal, owner kind, and purpose.

Instructions

Build a suggested connection_id, tags, and metadata object for a managed connection.

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": {
      "environment": "<environment>",
      "providerConfigKey": "<providerConfigKey>",
      "principal": "<principal>",
      "ownerKind": "<ownerKind>",
      "purpose": "<purpose>"
    },
    "name": "build_connection_convention"
  }
}

Input Schema

Name	Required	Description	Default
`purpose`	Yes
`ownerKind`	Yes
`principal`	Yes
`environment`	Yes
`oauthAppOwner`	No
`providerConfigKey`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2.0.0Aug 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

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 / 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"
+]

First observedv0.1.0Jun 12, 2026

TDQS

C2.6/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 disclosing side effects and behavior. 'Suggested' hints that the tool does not apply changes, but the description never states that it is non-persistent, read-only, or side-effect free, and it says nothing about authentication or failure behavior.

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, direct sentence with no filler and the core output is front-loaded. It is concise, though its brevity contributes to the lack of usage and parameter detail captured 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?

Despite having an output schema, an agent cannot safely call this tool: there is no parameter guidance, no usage context, and no behavioral guarantee beyond the word 'suggested.' For a six-parameter tool with no annotations, a one-sentence description is materially incomplete.

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 maps no parameters to the suggested output. An agent is left to infer the meaning and format of environment, providerConfigKey, principal, ownerKind, purpose, and oauthAppOwner from their names alone.

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 uses a specific verb ('Build') and names a concrete output: 'a suggested connection_id, tags, and metadata object for a managed connection.' It is clear about the resource and the fact that this is a suggestion, which helps separate it from apply_connection_convention, though it does not explicitly name sibling alternatives.

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 instead of alternatives such as apply_connection_convention, describe_connection_convention, or audit_connection_conventions. The single sentence gives no context about preconditions or intended workflow.

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