Skip to main content
Glama
TsvetanG2

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

create_handover_provider

Creates a handover provider in Cognigy.AI to escalate conversations to live agents, using a service from list_handover_services. Set dryRun=false to create it.

Instructions

Creates a new Cognigy.AI handover provider for live agent escalation, based on one of the services from list_handover_services. The provider starts with the service's default properties; change them with update_handover_provider. MUTATING: Set dryRun=false to create.

Input Schema

NameRequiredDescriptionDefault
nameYesName for the handover provider
typeYesHandover service name as returned by list_handover_services (e.g., 'liveAgent', 'salesforce', 'genesysCloud', 'chatwoot')
dryRunNoIf true (default), validates without creating. Set to false to actually create.
projectIdYesThe project ID to create the handover provider in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • removedInput schema / properties / enabled
      Removed value: -{
-  "default": true,
-  "description": "Whether the provider is enabled",
-  "type": "boolean"
-}
    • removedInput schema / properties / settings
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Provider-specific configuration settings",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}
    • changedInput schema / properties / type / description
      Previous value: -"Provider type (e.g., 'salesforce', 'genesys', 'ringcentral', 'custom')"New value: +"Handover service name as returned by list_handover_services (e.g., 'liveAgent', 'salesforce', 'genesysCloud', 'chatwoot')"
  2. First observedv0.1.4

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is partly covered. The description adds real behavioral context beyond that: the call is MUTATING, it is a no-op unless dryRun=false, and the created provider inherits the service's default properties rather than requiring full configuration.

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 what the tool creates and the prerequisite sibling, followed by follow-up guidance and the mutation warning. No filler; the dryRun restatement is a safety-critical confirmation rather than padding.

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 create tool with full annotations and 100% schema coverage, the description covers prerequisites, mutation semantics, and follow-up workflow. It does not mention what is returned (the created provider object), but with no output schema that is a minor omission rather than a blocker.

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 all four parameters (including dryRun's default-validates semantics and type's example values) are already documented. The description reinforces type's provenance and the default-properties behavior but adds no new syntax or format detail, so baseline 3 applies.

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 (Creates), resource (handover provider), platform (Cognigy.AI) and purpose (live agent escalation). It also anchors the tool to a sibling (list_handover_services) as the source of the service type, so an agent can separate it from list_handover_providers/get_handover_provider.

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: pick the service from list_handover_services, then use this tool; use update_handover_provider to change the resulting defaults. It also states the condition under which the call actually mutates (dryRun=false), which is exactly the guidance needed before invoking.

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