Skip to main content
Glama
TsvetanG2

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

create_connection

Creates a Cognigy.AI connection to store external service credentials such as API keys, passwords, or tokens; set dryRun=false to create.

Instructions

Creates a new Cognigy.AI connection for external service integration. Connections securely store credentials like API keys, passwords, and tokens. MUTATING: Set dryRun=false to create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the connection
typeYesConnection type as defined by the extension's connection schema (e.g., 'http-basic-auth', 'api-key')
dryRunNoIf true (default), validates without creating. Set to false to actually create.
fieldsNoConnection field values as key-value pairs (e.g., { apiKey: '...', baseUrl: '...' })
extensionYesName of the extension that defines the connection type (see list_extensions / get_extension)
projectIdYesThe project ID to create the connection in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • addedInput schema / properties / extension
      Added value: +{
+  "description": "Name of the extension that defines the connection type (see list_extensions / get_extension)",
+  "type": "string"
+}
    • changedInput schema / properties / type / description
      Previous value: -"Connection type (from extension schema, e.g., 'http-basic-auth', 'api-key', etc.)"New value: +"Connection type as defined by the extension's connection schema (e.g., 'http-basic-auth', 'api-key')"
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "name",
-  "type"
-]New value: +[
+  "projectId",
+  "name",
+  "type",
+  "extension"
+]
  2. First observedv0.1.4

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower, and the description still adds the critical dry-run default behavior and the fact that credentials are stored. It does not mention non-idempotency or permission requirements, but the dryRun disclosure is high-value context not conveyed by the annotations alone.

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 short sentences, front-loaded with the verb and resource, with the mutation/dryRun caveat given its own emphasized clause. Nothing redundant or padded.

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 6-param mutation tool with full schema coverage and no output schema, the description covers the essential trap (dryRun defaults to true so nothing is created unless overridden). It omits permission/scope requirements and any note about what identifiers the response returns, but nothing critical to correct invocation is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including the nested 'fields' object and 'type' examples is already documented in the schema. The description adds no syntax or format detail beyond that, which makes the baseline 3 the correct score.

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 ('Creates a new Cognigy.AI connection') plus the domain purpose ('external service integration') and what a connection holds (credentials, API keys, tokens). This cleanly separates it from the get_/list_/update_/delete_connection siblings in the same family.

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

Usage Guidelines3/5

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

The 'MUTATING: Set dryRun=false to create' line tells the agent how to actually perform the write rather than a dry run, which is genuinely actionable. However, it gives no routing against alternatives (update_connection for existing, list_extensions/get_extension for discovering the required extension) and no prerequisites such as permissions.

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